couchdb-replication mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Traun Leyden <>
Subject Question on replication process
Date Tue, 08 Jul 2014 13:42:06 GMT
I'm working on a 3rd party replication tool
<> in Go (currently Sync
Gateway compatible, but hopefully one day will be CouchDB compatible as
well), and I have a question on the replication process.

>From this replication algorithm description
and ladder diagram <>, if the
_rev_diffs response is empty, should it then skip steps 5 and 6 since there
is nothing to transfer and go straight to step 7?  (using the last_seq
value that was returned from source db _changes feed in step 3)

Or should it skip step 7 too and do another _changes request?

I'm guessing it's the former, since it seems like it should be safe to
forward the checkpoint if the _rev_diffs response is empty.  I haven't had
a chance to study the CouchDB replicator behavior yet, and thought someone
here might know off the top of their head.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message