-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2024-10-28, CAR Team 2024-11-25
-
1
The CheckMetadataConsistency hook currently relies on the discovery topology helpers, which uses the isMaster command in the background, to determine if the fixture cluster is sharded. Only then does it run the checkMetadataConsistency command.
Relying on the discovery topology and sending the isMaster command in the background to assess the fixture cluster's topology is not robust. This is due to various circumstances such as retriable errors, interruptions, unrelated network errors, etc., which have been added as acceptable retriable errors over time. See SERVER-85640, SERVER-82803, SERVER-94977, and SERVER-81340.
I propose that we modify the CheckMetadataConsistency hook so that it no longer relies on the discovery topology helpers. This change aims to reduce the likelihood of new retriable errors causing new BFs, which have not yet been accepted by the hook.
- related to
-
SERVER-81340 CheckMetadataConsistency hook is not compatible with integration_tests_sharded suite
- Closed
-
SERVER-82803 CheckMetadataConsistency hook should ignore NetworkInterfaceExceededTimeLimit errors
- Closed
-
SERVER-85640 Ignore network errors from connect in run_check_metadata_consistency.js
- Closed
-
SERVER-94977 CheckMetadataConsistency hook is not compatible with asio_transport_layer_integration_test
- Closed