-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 7.1.0-rc0
-
Component/s: None
-
Sharding EMEA
-
Fully Compatible
-
ALL
-
v7.1
-
Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13
-
5
-
1
CheckMetadataConsistency hook relies on the isMaster command to asses if the fixture cluster is sharded.
In the integration_tests_sharded suite we run at least two tests (1, 2) that set a failPoint to make the isMaster command to unconditionally fail, thus if the CheckMetadataConsistency hook runs while the fail point is set it will fail.
I can think of two possible solution here:
- Do not run the CheckMetadataConsistency hook in the intergration_tests_sharded suite
- Keep enable the hook on that suite but skip the speicifc tests that make the isMaster command to fail. We already did it in the past using this approach.
- is caused by
-
SERVER-76982 Enable CheckMetadataConsistencyInBackground in suites spawning a sharded cluster
-
- Closed
-
- is related to
-
-
- Closed
-
-
SERVER-94979 Make CheckMetadataConsistency hook don't rely on the discovery topology helpers
-
- Closed
-