New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replication: Persisting replications over a server restart #476

lupomontero opened this Issue Nov 5, 2012 · 0 comments


None yet
1 participant

lupomontero commented Nov 5, 2012


Im working on the Spanish translation and while working on the "Replication" chapter I realised the guide says:

At the time of writing, CouchDB doesn’t remember continuous replications
over a server restart. For the time being, you are required to trigger them
again when you restart CouchDB. In the future, CouchDB will allow you to
define permanent continuous replications that survive a server restart
without you having to do anything.

However, according to the Wiki (and my own experience) we have the _replicator database which was introduced in CouchDB 1.1.0 to persist replications. According to this gist linked on the WIki:

When CouchDB is restarted, it checks its _replicator database and restarts
any replication that is described by a document that either has its
_replication_state field set to "triggered" or it doesn't have yet the
_replication_state field set.

Note: Continuous replications always have a _replication_state field with
the value "triggered", therefore they're always restarted when CouchDB is

In the guide there is also no mention of the New features introduced in CouchDB 1.2.0

It would be great if we could update this chapter with the latest info. Should I attempt updating this chapter and send a pull request? Or is this something one of the authors should look at?



Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment