-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
Fully Compatible
-
ALL
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
SERVER-117145 introduces multi-router support to sharding test suites. However, failpoints are defined in individual processes, meaning that their values need to be manually updated across all mongos instances in the cluster (as well as mongod instances). Without this, there is a risk of inconsistent behavior, as commands could be processed by different mongos routers with different failpoint settings.
To address this, we need to implement a function that sets the failpoint value on all mongos and mongod instances in the cluster. The query optimization tests that modify the QO failpoints (disablePipelineOptimization and disableMatchExpressionOptimization) should be updated to use this new function.
Useful links:
- runCommandOnAllShards - this function run a commond on all mongod instances (we also need to run on all mongos instances)
- getAllMongosConnections - this function get a list of all mongos instances.
- is caused by
-
SERVER-117145 Integrate remaining aggregations_* suite with Multi-Router
-
- Closed
-
- is related to
-
SERVER-120547 MultiRouterMongo: Refer to the fail point utils introduced in SERVER-119161
-
- Closed
-
-
SERVER-120546 MultiRouterMongo: Refer to the fail point utils introduced in SERVER-119161
-
- Open
-
- related to
-
SERVER-120260 Ensure consistent failpoints even with the MultiShardedClusterFixture
-
- Open
-