Avoid change streams latency caused by lack of writes on a shard

XMLWordPrintableJSON

    • Query Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Query Execution
            Reporter:
            Katya Kamenieva
            Votes:
            5 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated: