Resharding recipient secondaries ignore no-op oplog entries meant to bump config.transactions records

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Sharding 2021-01-25
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SessionUpdateTracker::_updateSessionInfo() expects that {fromMigrate: true} has been set on the no-op oplog entry for it to be added as a derived operation to the oplog batch applied by secondaries.

      // Ignore any no-op oplog entries, except for the ones generated from session migration
// of CRUD ops. These entries will have an o2 field that contains the original CRUD
// oplog entry.
>if (entry.getOpType() == OpTypeEnum::kNoop) {
    if (!entry.getFromMigrate() || !*entry.getFromMigrate()) {
        return;
    }

    if (!entry.getObject2()) {
        return;
    }
}

              Assignee:
              Randolph Tan
              Reporter:
              Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: