[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: entryCSN is larger (later) in consumer node than in provider node
- To: Quanah Gibson-Mount <quanah@zimbra.com>
- Subject: Re: entryCSN is larger (later) in consumer node than in provider node
- From: Frank Luo <frank.luoy@gmail.com>
- Date: Tue, 24 May 2016 11:37:13 -0400
- Cc: openldap-technical@openldap.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=x4nv1Cjxt/LdByBxE2zhvfGYcLI+EJQGbW7BPwt6JMI=; b=VbfZ4jDM6P0IXBIc4Qp1Fb2FnXBS7I1Uho7LSFwGLQ+Jb7AJkAXOZodLcI50uCj0U5 YRf0KqKEHNwTU8OrwuPdPRQM7Q+ALDnLGQmWmX0kprqutNNgXwx8Y+hmgwqG+nj9XEOU yt3OKwnRFVTl9MmDOUziDP7+Kd9Dvw6pn8kHHJL+Hf70ECmxqW1Ep86Q9IvEIXeYNfDr bjiqQDYYPJ1Ywn0Q9ny6IjzeN8fw0eWWQqsXJEYWtlStxiwwiCjHt+0yxjwVHaHI+cQv AifTBLHMm4vcQgQ+t8XUTmMqW2nMoWmFC3e5WWL8UZYidfmTpbwf0gvbjvNctbWz1Wsl llEw==
- In-reply-to: <F7BFA5BFA93A0DDC28C3CFDD@192.168.1.19>
- References: <CAPdEfVKcYr0VzLWQB=4mtXJ_ayLp9Qq+Y90Rh0mitFR6wi=M6w@mail.gmail.com> <F7BFA5BFA93A0DDC28C3CFDD@192.168.1.19>
Thanks. The two servers were off by 15 seconds
I also checked contextCSN and see there were more than 1 values - any
idea there are multiple?
To help you understand we have a multiple(2) masters and three slaves.
on two masters (node1 and node 2), each has two contextCSN like this,
I can understand since they are in mirror mode, it get updates from
each other
node 1:
contextCSN: 20160524152519.525094Z#000000#001#000000
contextCSN: 20160524152340.159717Z#000000#002#000000
node 2:
contextCSN: 20160524152519.525094Z#000000#001#000000
contextCSN: 20160524152340.159717Z#000000#002#000000
on three slavers (nodes3,4 and5), each has 3 contextCSN. Where does
the third contextCSN come from - you can see the third one is out of
sync with each other.
node 3:
contextCSN: 20160524152519.525094Z#000000#001#000000
contextCSN: 20160521215740.310825Z#000000#000#000000
contextCSN: 20160524152340.159717Z#000000#002#000000
node 4:
contextCSN: 20160524152519.525094Z#000000#001#000000
contextCSN: 20160524152558.806951Z#000000#000#000000
contextCSN: 20160524152340.159717Z#000000#002#000000
node 5:
contextCSN: 20150723095205.352520Z#000000#000#000000
contextCSN: 20160524152519.525094Z#000000#001#000000
contextCSN: 20160524152340.159717Z#000000#002#000000
THanks
Frank
On Mon, May 23, 2016 at 5:11 PM, Quanah Gibson-Mount <quanah@zimbra.com> wrote:
> --On Monday, May 23, 2016 5:56 PM -0400 Frank Luo <frank.luoy@gmail.com>
> wrote:
>
>> All,
>>
>> I am having a out-of sync situation now with some entries' entryCSN
>> is larger (later) in consumer node than in provider node. So the
>> consumer never gets updated since it thinks it has the latest value.
>
>
> Check the clocks on each server. It is required that your clocks be tightly
> sync'd.
>
> --Quanah
>
>
> --
>
> Quanah Gibson-Mount
> Platform Architect
> Zimbra, Inc.
> --------------------
> Zimbra :: the leader in open source messaging and collaboration
> A division of Synacor, Inc