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

Clear _startAfterInvalidate when the resume token is observed in DSCSCheckInvalidate

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Query Execution 2021-07-26

      In SERVER-57792 we changed DSCSCheckInvalidate to throw the resume token up to DSCSEnsureResumeTokenPresent when starting after an invalidation event. However, when this happens we do not clear the value of the _startAfterInvalidate field; if the next thing the stream sees is another invalidating command, we will swallow it instead of invalidating the stream.

            Assignee:
            rishab.joshi@mongodb.com Rishab Joshi (Inactive)
            Reporter:
            bernard.gorman@mongodb.com Bernard Gorman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: