-
Type:
Task
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding EMEA
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Currently, the listCollections command on mongos uses DBClientReplicaSet::query, which does not retry on NotMaster errors.
This is a problem for concurrency stepdown suites (like the config stepdown suite introduced in SERVER-30677), that call listCollections through mongos as part of validating the state of the cluster between workloads, and because shardCollection, which is also called between workloads, involves calling listCollections and can fail if the config server has a stale view of the cluster.
The same is true for listIndexes, which uses the same cursorCommandPassthrough helper.
- is duplicated by
-
SERVER-36325 mongos will not retry configsvrShardCollection when it gets a not master error calling listIndexes
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-