-
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
The per-collection recordIdsReplicated option is retired and rid replication becomes node state, so the field no longer describes anything. This ticket replaces its original motivation (the field is shard-local and misleading in sharded clusters) with removal from listCollections output.
Details
- listCollections stops emitting recordIdsReplicated at active FCV (9.0+). At downgraded FCV the field keeps appearing for version-appropriate output.
- Delete the mongos-side stripping special case (cluster_list_collections_cmd.cpp), which currently removes recordIdsReplicated and fastCount from the primary shard's response because they are shard-local.
- The option was never vended on Atlas Core and is internal on Atlas Infinite, so no external consumer is expected to read it.
Acceptance criteria
- listCollections output at active FCV contains no recordIdsReplicated field, sharded or not.
- The mongos stripping code is deleted.
- Downgraded-FCV output keeps the field.
- depends on
-
SERVER-138124 Membership-based recordId emission and honoring in the oplog path
-
- Open
-
- related to
-
SERVER-133569 Skip recordIdsReplicated catalog consistency check per-node instead of per-suite
-
- Closed
-