couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Calle Arnesten <>
Subject Re: Problem with restart of continuous replication
Date Tue, 23 Apr 2013 09:05:24 GMT
Thanks for your answer.

I was using persistent _replicator. It was set up like this from both ends:
curl -X PUT -d "{ \"source\":\"<LOCAL_DB>\", \"target\":\"<REMOTE_DB>\", \"continuous\":true
                 <REMOTE>/_replicator/<A_NAME> -H "Content-Type:application/json"

The strange thing was that after the 2 hour communication problem, the replication was automatically
restarted on one of the ways but not the other way. 


On Tue, Apr 23, 2013, at 10:15, Robert Newson wrote:
> I recommend using the persistent _replicator replication manager, it
> will restart your replication jobs after a crash. POST's to _replicate
> with continuous:true will continue until a) the connection is severed
> or b) the node reboots, whichever comes first.
> B.
> On 23 April 2013 03:01, Calle Arnesten <> wrote:
> > Hi,
> >
> > I have a two-way continuous replication set up between two servers with CouchDB.
About a week ago we had a DNS problem that caused the machines to not to be able to communicate
for almost 2 hours. My assumption was that CouchDB would automatically try to restart the
replication. When I double-checked this a day or two later, replication was only restarted
for one way and not both. After rebooting the machine the replication started working both
ways again.
> >
> > Now my question is: Was my assumption wrong that replication should be restarted
automatically? If not, what could be the cause of it not working? The machine that it happened
to have CouchDB 1.2.1 installed.
> >
> > Also, do you have any recommendations on how to monitor that replication works and
notify by mail when it doesn't?
> >
> > /Calle

View raw message