[
https://issues.apache.org/jira/browse/COUCHDB-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240988#comment-15240988
]
Ivan Epifanov commented on COUCHDB-2289:
----------------------------------------
Digging dipper (this is correct for 1.6.1):
Looks like MAX_WAIT check only done in couch_replicator_api_wrap.erl (but
anyway done wrong, as it's multiplied by 2 twice:
Wait = 2 * erlamg:min( Wait0 * 2, ?MAX_WAIT)
But, there's no check in couch_replicator.erl#read_changes
Moreover, it uses single field httpdb.wait for both retry timeouts, and doen't
seem to reset it ever.
> 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)
