SERVER-48526ClosedFixed

Lengthy oplog scans may cause difficulty resuming change streams in a sharded cluster

If a change stream is resumed in a sharded cluster, all shards that have no oplog entries for the relevant namespace (either because they never had any data for the collection, or because they have not taken any writes recently) will scan through their oplogs until reaching EOF before returning their first {{getMore}} batch to {{mongoS}}. If the oplogs are large and the requested resume point is early, then this may take so long that the cursors on shards which *do* have oplog entries time out,

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
9.0.0-rc0
Components
Server components related to this issue
Aggregation FrameworkChange streams
Labels
Tags and classification
change-streams-improvements