change_metadata_consistency.js often attempts to access to the config server for inserts or updates in order to force an inconsistency and make sure those would be check by the
{ checkMetadataConsistency ... }command.
The test seems to access through direct connections to the CSRS in several points such here or here
This can be problematic in case of a stepdown suite, where the insert/update would fail without being retried.
The goal of this ticket is either to:
- fix all the direct connection with the config server
- ban the test from stepdown suites
Evaluate if point 2 still make sense. The goal of this jstest seems be the idea of catching some forced inconsistencies and not to simulate a possible user scenario.
- related to
-
SERVER-92339 Test runner can fail on network errors when talking directly to config shard in continuous config stepdown suite
- Closed