directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Ayyagari (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-1704) Inconistency in Master-Slave Replication
Date Mon, 09 Apr 2012 15:17:16 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249863#comment-13249863
] 

Kiran Ayyagari commented on DIRSERVER-1704:
-------------------------------------------

I think you are trying to replicate ou=system partition, there is one branch(ou=consumers,ou=system)
under ou=system that keeps details about the replication clients
that are connected which should ideally be bypassed but is not in reality.
One workaround is to move all your data to a new partition and configure replication for that
partition.
                
> 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
>              Labels: replication
>
> 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

        

Mime
View raw message