ExportXMLWordPrintableJSON

    • 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

      Flip both ends of the rid pipeline from the per-collection recordIdsReplicated catalog option to groupId membership in one commit: a primary emits rids iff it holds a groupId, and an applier honors them iff it holds a groupId.

      Details

      • Emission: the op observer already sets the rid (oplogEntry.setRecordId in op_observer_impl.cpp). The change is gating it on the membership plus the in-scope predicate instead of the per-collection catalog option. Holding a groupId implies flag-on plus latest FCV, since miniting only happens under both.
      • Honoring: relax tassert for rid presence iff collection option to a membership-plus-in-scope check.
      • In-group: inserts at the replicated rid, updates and deletes located by rid (existing computeEffectiveRid machinery).
      • Out-of-group: inserts generate local rids (today's non-rrid behavior), updates and deletes fall back to _id-based lookup.
      • Honoring is active in all application modes: steady state, initial sync application phase, and startup oplog recovery.
      • Emission and honoring must flip atomically. Emitting membership-based while honoring catalog-based (or vice versa) creates states where an in-group applier expects rids a groupless primary never wrote, or a primary emits rids an out-of-group applier ignores, both surfacing only as data divergence.
      • No behavior change for converged sets: an all-in-group replica set behaves exactly like today's flag-on behavior, so the existing featureFlagRecordIdsReplicated-tagged tests stay green.

      Acceptance criteria

      • Entries carry rids for in-scope collections iff the primary hols a groupId and none when groupless.
      • In-group nodes apply inserts at the replicated rid and locate updates and deletes by rid.
      • Out-of-group nodes ignore rid entirely.
      • Unit tests for in-group and out-of-group application of insert, update, and delete.
      • jstest with a mixed-membership replica set validating both paths.
      • Existing featureFlagRecordIdsReplicated-tagged tests pass.

            Assignee:
            Unassigned
            Reporter:
            Ernesto Rodriguez Reina
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: