-
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 test pauses collMod after the global catalog update but before shard-local updates, catches up the secondaries, then stops replication on one secondary. It resumes collMod and verifies that metadata consistency checking at the lagged secondary’s timestamp does not report a spurious CollectionOptionsMismatch. Finally, it restarts replication and checks consistency again. Under DSC, stopServerReplication() invokes a fixture-wide override that stalls primary log progress rather than pausing only the selected secondary. This prevents collMod from committing and eventually triggers the primary’s health-check shutdown.
As part of this ticket, we should 1) Adapt the test for DSC, and 2) Add the check_metadata_consistency_collmod_frozen_chunk_operations.js test to no_passthrough_disagg_override_replsets suite.
- related to
-
SERVER-138700 Investigate noPassthrough sharding coverage for tests applying replication lag injection
-
- Closed
-