Return-Path: X-Original-To: apmail-directory-users-archive@www.apache.org Delivered-To: apmail-directory-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DF13310438 for ; Sun, 22 Sep 2013 05:35:12 +0000 (UTC) Received: (qmail 59084 invoked by uid 500); 22 Sep 2013 05:35:10 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 58906 invoked by uid 500); 22 Sep 2013 05:34:58 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 58896 invoked by uid 99); 22 Sep 2013 05:34:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Sep 2013 05:34:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ayyagarikiran@gmail.com designates 74.125.82.178 as permitted sender) Received: from [74.125.82.178] (HELO mail-we0-f178.google.com) (74.125.82.178) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Sep 2013 05:34:50 +0000 Received: by mail-we0-f178.google.com with SMTP id u57so1873949wes.23 for ; Sat, 21 Sep 2013 22:34:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=288MQjCKR/1uoGVXZf+reJgS8yOpRc5iIHWsWDnC8is=; b=vI20b/JR2yUEgXBurst+JTATgC0Xz2tW26urj4AS5RAHIVKMfFGxR0JvyyNk5Mhl7U sgykbHnBEUWZweUcEil2+1QtELdIGuY+ltWUuJAsX80ax9qxhyjg+LE/e2o3T+xbsXI9 9vVbJGNQiMP1XdXPvF/6GLo3+HSkOaT7Nsaijz2h82TKe4fWz9g7nP4osCGHIQVhOgCR JgRO9ruqOqDKz9Fy04uWy5D1CA3NWnZktT6T4fvnpMuUEnDzBoeB+hgCiSgB2PeQkCb5 uwDf3wpbLXy1vXRmhoAJuvesEGBrYJfAYpCjYwPuE+9tnojECxsSYStSSvRYn9pjZiIr /KAg== MIME-Version: 1.0 X-Received: by 10.180.81.71 with SMTP id y7mr8507048wix.63.1379828069389; Sat, 21 Sep 2013 22:34:29 -0700 (PDT) Sender: ayyagarikiran@gmail.com Received: by 10.216.245.200 with HTTP; Sat, 21 Sep 2013 22:34:29 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Sep 2013 11:04:29 +0530 X-Google-Sender-Auth: hqbPRqMfsgF-H5Vf2YRzxLpZTHI Message-ID: Subject: Re: Questions About Master-Master Replication From: Kiran Ayyagari To: users@directory.apache.org Content-Type: multipart/alternative; boundary=f46d04428cc2ede10a04e6f2413f X-Virus-Checked: Checked by ClamAV on apache.org --f46d04428cc2ede10a04e6f2413f Content-Type: text/plain; charset=ISO-8859-1 On Sun, Sep 22, 2013 at 12:35 AM, Gareth Collins wrote: > Hello, > > I see that ApacheDS 2.0 supports Master-Master replication which is great > (based on RFC 4533)! I understand that Master-Master replicas will have > eventual consistency? > yes > > Are there any potential "gotchas" setting up Master-Master replication. > e.g.: > > (1) Anything special you need to do in the case of a network partition? > > if a peer is unavailable then the server will keep checking for its availability in regular intervals and meanwhile stores all the modifications in a log which will be sent when the peer come back online. > (2) Are there any scenarios where Apache DS Master-Master instances > can get into a state where they cannot synchronize (i.e. a conflict) which > would require manual intervention? If yes, how would a user know that > a conflict exists? > > not any that I have run into, but I will depend on the contextCSN value stored in ou=system of each server to detect if they are in sync i.e when two servers A and B are in M-M mode then they are in sync if there is an entry Eb in B with the entryCSN attribute value matching with the contextCSN value of A and vice versa. Any info here, would be a bug help! > > thanks in advance, > Gareth > -- Kiran Ayyagari http://keydap.com --f46d04428cc2ede10a04e6f2413f--