GitHub user nickva opened a pull request:

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

    Switch replicator manager change feeds to "longpoll"

    Fixes replication manager rescans on cluster membership
    change.
    
    Replication manager resets all replication db
    sequence checkpoints, and starts a new replicator db
    background scanner.  Each replicator database is signaled
    to rescan from sequence 0. However previous change feeds
    for each db have to exit first. If they never exit, because
    they are "continuous" new change feeds will never start.
    
    Putting change feeds in "longpoll" mode ensures they will
    eventually exit.
    
    JIRA: COUCHDB-2963

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

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

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

    https://github.com/apache/couchdb-couch-replicator/pull/30.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 #30
    
----
commit a7e7565d6a743961ebdec155fbfd70f609337ce2
Author: Nick Vatamaniuc <[email protected]>
Date:   2016-03-04T20:06:41Z

    Switch replicator manager change feeds to "longpoll"
    
    Fixes replication manager rescans on cluster membership
    change.
    
    Replication manager resets all replication db
    sequence checkpoints, and starts a new replicator db
    background scanner.  Each replicator database is signaled
    to rescan from sequence 0. However previous change feeds
    for each db have to exit first. If they never exit, because
    they are "continuous" new change feeds will never start.
    
    Putting change feeds in "longpoll" mode ensures they will
    eventually exit.
    
    JIRA: COUCHDB-2963

----


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

Reply via email to