Change streams should resume indefinitely after each successful aggregate

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical - P2
    • 4.12.0
    • Affects Version/s: 4.8.0
    • Component/s: None
    • 3
    • Not Needed
    • None
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      This commit changed the resumibility behavior for change streams.

      Change streams should attempt to resume once on a resumable error and once successfully resumed, they should treat any errors on subsequent getMores as resumable and attempt to resume.

      The commit linked above changes this behavior to the following:

      • in the case of a resumable error, we resume once
      • if another error occurs before a change event is received, we immediately close the change stream and make no attempt to resume.

      Acceptance Criteria

      • Ensure that after a successful resume, any subsequent getMore errors before a change event is received do not close the change stream

              Assignee:
              Bailey Pearson
              Reporter:
              Bailey Pearson
              Neal Beeken
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: