Change stream cursor does not resume when attempt to kill the existing cursor fails

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.4, 3.7.0
    • Affects Version/s: 3.6.0
    • Component/s: Query Operations
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The change stream specification test plan says:

      The killCursors command sent during the “Resume Process” must not be allowed to throw an exception

      This was not properly implemented in the driver. In particular, if the attempt to get a connection on which to send the killCursors commands results in a ConnectException, then that exception will be thrown instead of being suppressed. As a result, if the attempt to kill the cursor fails (as when the server with the cursor is shut down) then the driver will not properly resume the change stream cursor and instead throw the exception.

              Assignee:
              Jeffrey Yemin
              Reporter:
              Jeffrey Yemin
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: