-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
None
-
None
-
None
-
None
-
None
-
None
-
None
replicate_record_ids_dbhash.js was disabled as it asserts the old per-collection semantics: dbHash catches injected rid divergence only when the collection has recordIdsReplicated: true, and ignores it otherwise. Under the set-wide groupId design, rid inclusion in the hash is a function of node membership and the in-scope predicate, not a per-collection catalog flag.
Change
Re-enable the test and rewrite it around membership states:
- In-group nodes: inject rid divergence (the existing explicitlySetRecordIdOnInsert failpoint approach) and assert checkReplicatedDataHashes throws.
- Out-of-group node (groupId cleared via the C1 or C3 path): inject the same divergence and assert the hash check passes, since out-of-group nodes hash document contents only.
- depends on
-
SERVER-138127 Re-enable rid-sensitive dbHash checks in test fixtures with groupId-membership-aware opt-in
-
- Open
-
- related to
-
SERVER-139451 Restrict the fixture dbHash rid opt-in to disagg until groupId membership lands
-
- In Code Review
-