couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Shorin <kxe...@gmail.com>
Subject Re: Using _active_tasks to track continuous replication status
Date Wed, 29 Jul 2015 14:46:51 GMT
Hi,

Two ways:

1) Get document revision on source side. Continuously HEAD request
that document with the same revision on the target side until 200 OK
response.
2) Get document local_seq on source side. Watch replication status on
_active_tasks until completed sequence will be equal or great
document`s one.

--
,,,^..^,,,


On Wed, Jul 29, 2015 at 5:40 PM, Foucauld Degeorges <foucdeg@gmail.com> wrote:
> Hi all
>
> I'm trying to figure out a way to know whether a document has been
> effectively replicated (in continuous mode) to a remote CouchDB, with a
> minimum of network requests.
> My first idea would be to compare the date of the document creation /
> modification against the date of the last successful replication . How do I
> get the latter?
>
> The _actve_tasks api gives me a updated_on value which seems to just be the
> date the _active_tasks document was generated, but the rest of the doc
> might indicate other things, like "that last replication didn't go so
> well". There are also sequence numbers which look like they tell me the
> last sequence that was succesfully replicated. I find the documentation
> unclear about _active_tasks.
>
> Has anyone done this before?
>
> Cheers
> Foucauld Degeorges

Mime
View raw message