Uploaded image for project: 'CouchDB'
  1. CouchDB
  2. COUCHDB-2963

Replication manager does not rescan databases on cluster membership change

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              kzx kzx
              Reporter:
              vatamane Nick Vatamaniuc
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: