Add OplogVisibilityManager calls under feature flag at getOplogManager callsites

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Repl 2025-07-21, Repl 2025-08-04, Repl 2025-08-18
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Using the feature flag for SPM-3556, add calls (demonstrated below) to all callsites that currently acquire the WT oplog manager, and add calls to the new visibility manager. This connects the "read" side of the new datastructure to other consumers in other modules.

      if (gFeatureFlagOplogVisibility) {
        auto* opvis = repl::OplogVisibilityManager::get(opCtx);
        return opvis->getOplogVisibilityTimestamp();
      else {
        return getOplogManager()->getOplogReadTimestamp();
      }

      There are other related calls on the old oplog manager that can also be replaced with their equivalents on the new oplog visibility manager. Notably, this ticket encompasses calls to waitForAllEarlierOplogWritesToBeVisible which is the majority of uses of both the old and new visibility systems.

            Assignee:
            Unassigned
            Reporter:
            Myles Hathcock (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: