[
https://issues.apache.org/jira/browse/COUCHDB-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180670#comment-15180670
]
Nick Vatamaniuc commented on COUCHDB-2963:
------------------------------------------
Even though "longpoll" mode would work we could investigate using "normal"
change feeds.
Created separate ticket to track tha:
https://issues.apache.org/jira/browse/COUCHDB-2964
> 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)
