Github user nickva commented on the pull request:
https://github.com/apache/couchdb-couch-replicator/pull/37#issuecomment-215300013
@kxepal
Ah I see what you meant. Yeah it might be possible to have a batcher for
doc updates.
In general it would be better to not have to write back do docs on every
error. Or not have to write back to docs at all ;-) Now when retries happen
(especially if they happen at the same time due to common source failure) all
retires will write errors to docs, which will kick off change feeds, which will
be noticed by replicator manager at the same time restarts are also happening.
So it creates a positive feedback loop.
As for other question, noticed issues on a cluster with 1000 or so
replications. There were other pecuilarities about it, but it manifested these
sharp load spikes -- when a few things failed, it triggered other events, which
added even load and then more failures and so on.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
