[
https://issues.apache.org/jira/browse/COUCHDB-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240855#comment-15240855
]
Ivan Epifanov commented on COUCHDB-2289:
----------------------------------------
I'm not sure, but i have similar problem. Replication just stalls at some point
on 1.5.0
Doing some digging in logs, turns out, if source database wasn't updated for
some time (connection_timeout in replicator config), slave restarts request.
Every time it does so, it doubles timeout for retry, even if it's already at
different checkpoint.
Once retry timeout reaches 65536.0 seconds (which it shouldn't, according to
docs it shouldn't exceed 5 mins) replication stalls completely.
> Replication stall
> -----------------
>
> Key: COUCHDB-2289
> URL: https://issues.apache.org/jira/browse/COUCHDB-2289
> Project: CouchDB
> Issue Type: Bug
> Components: Replication
> Reporter: Gil Pedersen
>
> I have 2 couchdb instances in a local setup with one acting as the master,
> and the other performing a continuous pull replication using the _replicator
> db.
> This was initially working great but now I occasionally experience permanent
> stalls in the replication. I can get it running again by restarting the
> couchdb instance but it will eventually stall again.
> Gist with more info here: https://gist.github.com/kanongil/9788322
> I have also tried to create a 1.6.0 docker-based instance which also stalls
> (but at different sequence numbers).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
