Oh. Thx. I guess this should be mentioned in the official documentation, not only in the comment section of an offsite doc. :-) T 2013.05.16. 14:01, "svilen" <[email protected]> ezt írta:
> from the doc: https://gist.github.com/fdmanana/832610 > * >What is the recommended way to restart a replication that > * is currently in the error state? > * Edit the doc and remove the field "_replication_state". > * Or create another identical doc (same source, target, etc). > > > On Thu, 16 May 2013 13:52:46 +0200 > Tibor Gemes <[email protected]> wrote: > > > I have a notebook on which there is a couchdb instance. I have a > > continuous replication document in the _replicator database. > > Let's suppose I suspend my notebook and wake it up in a different > > network where there is no network connection. The replication > > document switches its state to error. > > If I later move back to a different network where I can reach the > > source couchdb again then the replication will turn to 'triggered' > > after a while, but how can I enforce it to recheck the remote end? Is > > there any api call which would force to revalidate the state of the > > replication? > > > > T >
