-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
(copied to CRM)
In a sharded cluster, to guarantee total ordering of events, change stream checks for events on all shards. This constrains latency of the events in change stream by the largest latency between writes on any individual shard.
Default for periodicNoopIntervalSecs is 10s, so in the worst case when one of the shards doesn't receive any writes, the latency will be around that.
- related to
-
SERVER-30784 Allow sharded change streams to target just the shards that have chunks
- Backlog
-
SERVER-42290 Target change streams to the primary shard when possible
- Backlog
-
SERVER-44356 Change Stream latency is determined by config server write rate
- Closed