Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-couch-replicator/pull/37#issuecomment-215289304
@nickva
> We are thinking how to built that however that will take longer and will
be closer to a complete re-write of the replicator code.
I don't think you need to rewrite replicator code to add another manager
that receives messages with what update_rep_doc/3 gets and then by recurrent
event folds own queue into batch and reuses existed bulk_docs call against
replicator db (: Basically, sort of reducer.
But that's true, some more work that will require while random is quick fix
for the issue that just works in most of setups. I just though that Cloudant
has exactly large setups where that fix won't work well (;
But ok, thank you for explanation of the idea.
Few more questions, if you don't mind (:
What's the critical amount of replications when they massive update cause
issues? And the following one: does it worth to not sleep for quite short
periods e.g. small replications amount if they couldn't cause any issues?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
