-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Atlas Streams
-
Fully Compatible
-
Sprint 60
-
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
- is related to
-
SERVER-95499 Azure smoke test processor stopped processing messages
-
- Closed
-