Disregard that, please. The replication got actually stuck. I had to explicitly stop and then start it over.
What we do is we have a script that is executed by a cron job. The script has a few curl commands telling local couch to start pulling from remote servers. Used to work well on 1.1.1, but with 1.3.1 it seems to get stuck. Is there a better way to ensure that replication doesnt stop like that? Andrey On Thu, Aug 29, 2013 at 8:14 PM, Andrey Kuprianov < [email protected]> wrote: > Hi guys, > > I'm running a few pull replications and basically this is a mesh between 4 > servers (all of them are couch 1.3.1). Some of the replication statuses are > showing 100% progress but some seem to have stuck on a percentage below > 100. Like the one below: > > *Checkpointed source sequence 582782, current source sequence 626908, > progress 92% > ** > ** > * > > > * > * > I have checked replication by trying to save a document on one side and > checking it on the other and it works fine. Is status update showing wrong > values then or is there something else? > > Andrey >
