[
https://issues.apache.org/jira/browse/COUCHDB-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888707#comment-15888707
]
ASF subversion and git services commented on COUCHDB-3311:
----------------------------------------------------------
Commit 45d739af3fcf8b4f8e3ccca152cb3c2d781dc2fc in couchdb-couch-replicator's
branch refs/heads/master from [~vatamane]
[
https://git-wip-us.apache.org/repos/asf?p=couchdb-couch-replicator.git;h=45d739a
]
Restore adding some jitter-ed sleep to shard scanning code.
Otherwise a large cluster will flood replicator manager with potentially
hundreds of thousands of `{resume, Shard}` messages. For each one, it
would try to open a changes feed which can add significant load and has
been seen in production to hit varios system limits.
This brings back the change from before the switch to using mem3 shards
for replicator db scans.
Also adds a few tests.
COUCHDB-3311
> Restore jitter-ed sleep to replicator manager shard discovery
> -------------------------------------------------------------
>
> Key: COUCHDB-3311
> URL: https://issues.apache.org/jira/browse/COUCHDB-3311
> Project: CouchDB
> Issue Type: Bug
> Reporter: Nick Vatamaniuc
>
> Jitter-ed sleep or was dropped inadvertently when we switch to using mem3
> shards instead of scanning the file system.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
