Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-89130

Revert changes from SERVER-86741

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc5
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • Fully Compatible
    • v8.0
    • Repl 2024-04-15, Repl 2024-04-29, Repl 2024-05-13
    • 105

      Updating the config.transactions entry as part of setFeatureCompatibilityVersion downgrade causes the active primary to invalidate its TransactionParticipant's in-memory state. This can break assumptions of C++ code which runs on an active primary, for example, SERVER-88539 in chunk migration. We will instead take a different approach in SERVER-87563 for TransactionParticipant::Participant::refreshFromStorageIfNeeded() when the oplog entry from a higher FCV format cannot be parsed in the lower binVersion.

            Assignee:
            matthew.russotto@mongodb.com Matthew Russotto
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: