GhostSync::percolate() should refresh dead cursors with OplogReader::tailCheck()

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Critical - P2
    • 2.2.5, 2.4.3, 2.5.0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • ALL
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a ClientCursor is dropped between batches (or during a batch because of an exception like kill op) the DBClientCursor for this ClientCursor will become "isDead()". If the DBClientCursor 'cursor' held by an OplogReader is dead, OplogReader::haveCursor() still returns true. In order to detect cursors, OplogReader::tailCheck() must be called. GhostSync::percolate() should call OplogReader::tailCheck() before using an old cursor in its oplog reader. Otherwise, percolate() may repeatedly attempt to read from a dead cursor and fail to see any results.

              Assignee:
              Eric Milkie
              Reporter:
              Aaron Staple (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: