-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Querying, Replication, Sharding
-
Fully Compatible
-
v3.6
-
Repl 2017-10-23, Repl 2017-11-13, Repl 2017-12-04
-
0
Shards can return a 'retryNeeded' entry as part of a changeStream on a sharded collection. This happens when the shard recently donated a chunk for this collection to a shard that has no chunks for that collection. When a mongos encounters such an entry it needs to reload the shard registry (to pick up any recently added shards) and then establish changeStream cursors on any new shards it discovers. It will also need to filter out the 'retryNeeded' entry so it never gets back to the client.
- related to
-
SERVER-32085 $changeStream reports incorrect documentKey for unsharded collections that become sharded
- Closed
-
SERVER-31028 Reload shard registry and ensure set of shards hasn't changed when establishing sharded change stream cursors
- Closed
-
SERVER-31978 Add an invariant that DocumentSourceCloseCursor does not execute on a mongod for a sharded $changeStream
- Closed