Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAHdjipKOOvv47gVJwN4OZ6Dv_LfgVR1VPyx_cCLcUJt3hj9D-Q@mail.gmail.com>
References: 
 <CAD4LyZmiJjbw8jM-0rP4HBshHDRinFFE6bBoJ+ZiC2Qs7jDrzA@mail.gmail.com>
	<CAHdjipJMd=5vOGejRncHDjaxET-UQKpRm=RN7cL=Ou9cg=_Pkg@mail.gmail.com>
	<CAD4LyZn4JDmbyUpY-74GaRYfUWbv9DBaOWZ7XEOjNr8tY2+1Cw@mail.gmail.com>
	<CAHdjipKOOvv47gVJwN4OZ6Dv_LfgVR1VPyx_cCLcUJt3hj9D-Q@mail.gmail.com>
Date: Thu, 30 Jul 2015 10:19:16 +0200
Message-ID: 
 <CAD4LyZm1nS4fpKMzPAbZ0p5mX7gpfb+gMcQvWMneMnoobdtj4Q@mail.gmail.com>
Subject: Re: Using _active_tasks to track continuous replication status
From: Foucauld Degeorges <foucdeg@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=f46d043c8230ff9385051c135b8d

--f46d043c8230ff9385051c135b8d
Content-Type: text/plain; charset=UTF-8

Awesome, thanks.
Now, to push it a bit further, let's suppose I have three databases in
replication : A -> B -> C, and I need to know which document created in A
is the last one that got to C, so I can display a "synchronized / not
synchronized" symbol next to the various documents in my view.

To know which document got to C, here is my idea: using B's _active_tasks I
know which update sequence of B got to C. I query B's _changes feed to know
what document/revision that update sequence concerns. I query that same
document/revision on A using the local_seq option. Now I know which update
sequence of A is the last one that got to C, assuming that* sequences are
kept in the same order* through two replications.

Is that a safe assumption? Or can anyone think of a simpler way to do this,
without having to HEAD each document individually?

Foucauld


2015-07-29 17:18 GMT+02:00 Alexander Shorin <kxepal@gmail.com>:

> On Wed, Jul 29, 2015 at 6:13 PM, Foucauld Degeorges <foucdeg@gmail.com>
> wrote:
> > Just to clarify, by "completed sequence" you mean
> checkpointed_source_seq,
> > is that right ?
>
> Yes. This is an update sequence of source which is recorded in
> checkpoint what means that all the data up to that value are already
> replicated.
>
> --
> ,,,^..^,,,
>

--f46d043c8230ff9385051c135b8d--