Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-102106

ReshardingChangeStreamsMonitor should always update the resume token after each round instead of only when the number of matched events is non-zero

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • Cluster Scalability 2025-03-17

      Currently, after each round of getMore commands, the ReshardingChangeStreamsMonitor would only update the resume token in the donor/recipient state document when the number of matched events is non-zero. It is possible for the collection being monitored to not have any matched events (i.e. inserts and deletes) in some round or all rounds. Not updating the resume token means that the monitor would need to resume from the very start if a failover occurs.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: