Explicitly return a stream-fatal error in cases where a change stream cannot be automatically resumed

XMLWordPrintableJSON

    • Fully Compatible
    • v4.2, v4.0, v3.6
    • Query 2019-12-16
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      At present, change streams may throw a variety of different error codes depending on the specific failure it encountered, such as InternalError, TooManyMatchingDocuments, or an unnamed code like 40576. Drivers do not recognise these as non-resumable exceptions, which can lead them to enter an infinite retry loop on a sharded cluster.

            Assignee:
            Bernard Gorman
            Reporter:
            Bernard Gorman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: