Bug 782923 - document how to resolve replication conflicts
Summary: document how to resolve replication conflicts
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Identity_Management_Guide
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 6.3
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-18 21:04 UTC by Dmitri Pal
Modified: 2012-06-21 23:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-21 23:16:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dmitri Pal 2012-01-18 21:04:39 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2258

Originated from ticket 1025.

From 389-ds FAQ:

If conflicts occur, the conflict resolution algorithm will resolve them, and if that is not possible, the conflicts are flagged for viewing by the administrator.

Each modification is assigned a Change State Number (CSN) which uniquely identifies the modification. Part of the CSN is a timestamp, and part is the identifier of the master on which the change originated. The conflict resolution algorithm usually processes the changes such that the "last one wins" based on the timestamp, but there are many corner cases which require special handling (for example, if an entry is removed from one master and at the same time a child entry is added to that entry on another master). 

To find conflict entries see the 389-ds documentation at:

http://docs.redhat.com/docs/en-US/Red_Hat_Directory_Server/8.2/html-single/Administration_Guide/index.html#Managing_Replication-Solving_Common_Replication_Conflicts

Comment 4 Deon Ballard 2012-05-03 16:33:50 UTC
Setting all priority and severity to medium.

Comment 7 Deon Ballard 2012-06-21 23:16:24 UTC
Closing.


Note You need to log in before you can comment on or make changes to this bug.