-
Type:
Bug
-
Status: Closed
-
Priority:
Minor - P4
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Sharding, Testing Infrastructure
-
Labels:
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Backport Requested:v4.4
-
Sprint:Sharding 2020-09-21
-
Linked BF Score:0
The balancing_sessions_collection.js intentionally removes one of the shards before shutting down the ShardingTest. It is possible for mongos to refresh its ShardRegistry after choosing to target all shards with the $indexStats aggregation and then triggers a ShardNotFound error.
One proposal to address this issue is to retry running the $indexStats aggregation on ShardNotFound errors.