-
|
What can cause replication to get stuck? I have 3 couch instances: couchdb: couch 1.7 The replicators run in the couch 3.1.1 instances (see screenshots)
I've tried restarting the couch instances several times in the past few days but can't seem to get it to make progress. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
See if there are any errors in the logs or in the _scheduler/jobs for those replications If replications use a filter and it's fairly restrictive, there could be a large number of pending changes and very few writes. Another reason could be a validate doc update (VDU) function which is restricting writes. Without a more details job history and/or logs it's a bit hard to tell why state looks like that This might also be better converted to a discussion for now |
Beta Was this translation helpful? Give feedback.
See if there are any errors in the logs or in the _scheduler/jobs for those replications
If replications use a filter and it's fairly restrictive, there could be a large number of pending changes and very few writes.
Another reason could be a validate doc update (VDU) function which is restricting writes.
Without a more details job history and/or logs it's a bit hard to tell why state looks like that
This might also be better converted to a discussion for now