Mitigate stuck changestream bug by throwing exception after period of idleness

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Atlas Streams
    • Fully Compatible
    • Sprint 60
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We sometimes have a situation where a change stream source stops receiving new events even though the source database/collection has newer events.  As a workaround, we can detect such "stale" sources and restart the processor

              Assignee:
              Mayuresh Kulkarni
              Reporter:
              Matthew Normyle
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: