-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-11-09
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The lagged_config_secondary.js test verifies that mongos times out when the only reachable config-server secondary is behind the required metadata timestamp. The test currently uses stopServerReplication() to lag one secondary. Under DSC, this helper stalls primary-side replication across the replica set instead of pausing only the selected standby, so it does not preserve the intended scenario.
As part of this ticket, we should 1) Adapt the test for DSC, and 2) Add the test to no_passthrough_disagg_override_sharded suite.
- is related to
-
SERVER-139452 Add CAR ownership to jstests/sharding/lagged_config_secondary.js
-
- Needs Scheduling
-
- related to
-
SERVER-138700 Investigate noPassthrough sharding coverage for tests applying replication lag injection
-
- Closed
-