Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 27C8895D6 for ; Mon, 9 Apr 2012 08:47:47 +0000 (UTC) Received: (qmail 52181 invoked by uid 500); 9 Apr 2012 08:47:47 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 51957 invoked by uid 500); 9 Apr 2012 08:47:46 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 51271 invoked by uid 99); 9 Apr 2012 08:47:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2012 08:47:45 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2012 08:47:43 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id BB9C8361D3D for ; Mon, 9 Apr 2012 08:47:23 +0000 (UTC) Date: Mon, 9 Apr 2012 08:47:23 +0000 (UTC) From: "Amod Kadam (Created) (JIRA)" To: dev@directory.apache.org Message-ID: <1240860778.2089.1333961243782.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (DIRSERVER-1704) Inconistency in Master-Slave Replication MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Inconistency in Master-Slave Replication ---------------------------------------- Key: DIRSERVER-1704 URL: https://issues.apache.org/jira/browse/DIRSERVER-1704 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M6 Environment: OS : Windows XP Professional Version 2002, Service Pack 3 Hardware : Intel 1.73 Ghz, 2 GB RAM Reporter: Amod Kadam Priority: Critical We are testing master-slave configuration for ApacheDS and observed inconsistency when data from MASTER gets deleted. The record gets deleted from MASTER but does not get deleted from SLAVE. However this does not happen always. Secondly we are unable to find out the pattern for the same. We have seen this issue after executing the Test Cases in sequence. Scenario - Master changes state from RUNNING to STOP and then RUNNING again while Slave is in 'RUNNING' state Ensure that MASTER and SLAVE are running before executing each test case. ======================================================== Test Case No: 1 1) Stop Master 2) Restart MASTER 3) Add an entry to the MASTER dn: cn=amodkadam,ou=users,ou=system objectClass: person objectClass: top sn: kadam cn: amodkadam Expected Result : SLAVE should get corresponding entry for dn: cn=amodkadam,ou=users,ou=system Actual Test Result: Same as expected result. =========================================== Test Case No:2 1) Stop Master 2) Restart MASTER 3) UPDATE an entry in the MASTER dn: cn=amodkadam,ou=users,ou=system objectClass: person objectClass: top sn: kadam_update cn: amodkadam Expected Result : SLAVE should have UPDATED entry for dn: cn=amodkadam,ou=users,ou=system Actual Test Result: Same as expected ================================================ 1) Stop Master 2) Restart MASTER 3) DELETE an entry from the MASTER dn: cn=amodkadam,ou=users,ou=system objectClass: person objectClass: top sn: KADAM cn: amodkadam Expected Result : Corresponding entry should be deleted from SLAVE but does not get DELETED Actual Result Fails and the record in the SLAVE does not get deleted. However this does not happen alwyas. ========================================================================= Could you let us know what could be issue and how to fix it ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira