-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 7.0.0, 8.0.0
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
CAR Team 2024-09-30
-
0
CheckMetadataConsistency hook relies on the discovery topology - which uses isMaster behind the scenes - to asses if the fixture cluster is sharded.
In the `asio_transport_layer_integration_test.cpp` unit test, a failpoint is enabled that causes `isMaster` command to fail during a specific window of time. If the checkMetadataConsistency is run between that windows of time, the test will fail.
Similar to SERVER-81340, the goal of this ticket is to skip running the CheckMetadataConsistency hook in the specific test `asio_transport_layer_integration_test.cpp` within the integration_tests_sharded suite.
- is related to
-
SERVER-94979 Make CheckMetadataConsistency hook don't rely on the discovery topology helpers
- Needs Scheduling
- related to
-
SERVER-81340 CheckMetadataConsistency hook is not compatible with integration_tests_sharded suite
- Closed