-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When we worked on SERVER-117714, we identified that it was difficult to isolate the condition of stale routing info and to verify fix we did an 'ugly' test which we did not checkin–in order to act quickly to resolve a hot BF.
This ticket is a follow up of SERVER-117714 to write a good test that runs as part of the test suite.
- is related to
-
SERVER-117714 ReshardingCoordinator may hit a tassert when accessing stale config metadata during the cloning phase
-
- Closed
-