[jira] [Commented] (COUCHDB-3311) Restore jitter-ed sleep to replicator manager shard discovery

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888697#comment-15888697 ] 

ASF GitHub Bot commented on COUCHDB-3311:
-----------------------------------------

GitHub user nickva opened a pull request:

    https://github.com/apache/couchdb-couch-replicator/pull/57

    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

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloudant/couchdb-couch-replicator couchdb-3311

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-couch-replicator/pull/57.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #57
    
----

----


> 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)