You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/03/04 21:22:40 UTC
[jira] [Commented] (COUCHDB-2963) Replication manager does not
rescan databases on cluster membership change
[ https://issues.apache.org/jira/browse/COUCHDB-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180493#comment-15180493 ]
ASF GitHub Bot commented on COUCHDB-2963:
-----------------------------------------
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 <va...@gmail.com>
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
----
> Replication manager does not rescan databases on cluster membership change
> --------------------------------------------------------------------------
>
> Key: COUCHDB-2963
> URL: https://issues.apache.org/jira/browse/COUCHDB-2963
> Project: CouchDB
> Issue Type: Bug
> Reporter: Nick Vatamaniuc
>
> Replication manager should rescan all replicator databases on cluster membership changes from sequence 0, in order to possibly pick up new replication it might be an owner of.
> On receipt of nodedown or nodeup message, replication manager attempts to start a new scan by resetting the checkpointed sequence IDs ets table. With the intent that change feeds will exit and then check if they need to rescan again. However because change feeds used for the replicator databases are "continuous" they never exit, so consequently they never get a chance start rescanning from 0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)