-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Storage Execution 2026-04-13, Storage Execution 2026-04-27
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In DSC, the PersistenceProvider requires that all collections have recordIdsReplicated. This makes the presence of the recordIdsReplicated field in the listCollections output unnecessary for DSC.
The recordIdsReplicated is still not enabled for ASC in production but we use it on the tests. For ASC it is currently needed for the Initial Sync process to keep the collection consistent in term of the recordIdsReplicated within a replica set. In ASC, we even allow collections to have mismatched values for recordIdsReplicated in different shards, that is why we removed the recordIdsReplicated field from the listCollection output from a mongos.
This is going to be reviewed as part of SERVER-122753 when we enable recordIdsReplicated for ASC, however, in order to keep it a two way door, lets remove the recordIdsReplicated field from the listCollections output of DSC.
- depends on
-
SERVER-122769 Remove recordIdsReplicated from mongos listCollections Output
-
- Closed
-
- is related to
-
SERVER-122753 Revisit listCollections Behavior Regarding recordIdsReplicated Field in Sharded Clusters
-
- Backlog
-
- related to
-
SERVER-122769 Remove recordIdsReplicated from mongos listCollections Output
-
- Closed
-