[
https://issues.apache.org/jira/browse/COUCHDB-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133494#comment-14133494
]
Daniel Carr commented on COUCHDB-2289:
--------------------------------------
This looks like something that happened to me once.
If you add another document to the source database, does
a) the new document show up in the target database
b) the active tasks looks fine (progress: 100, etc)
In this case the replication has not stalled, it's just that the last change
from source database can't be written to the target. This usually happens when
the last document to be changed / added on the source is a design document, and
the user who initiates the replication doesn't have permission to write _design
docs.
> Replication stall
> -----------------
>
> Key: COUCHDB-2289
> URL: https://issues.apache.org/jira/browse/COUCHDB-2289
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> 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)
