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

Replicator manager does not checkpoint properly

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0.0
    • None
    • Replication
    • None

    Description

      In couch_replicator_manager

       changes_reader_cb({stop, EndSeq, _Pending}, ...) -> 

      function at one point in the past was handling callback messages from fabric:changes and so it would get pending info in the callback messages. When it was optimized to use local shard, local changes feeds don't send stop messages.

      As a result replicator manager never checkpoints and on every change to a replicator shard, rescan all the changes in that shard.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              vatamane Nick Vatamaniuc
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: