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

Temporarily do not enforce constraints when fetching active transaction history

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution NAMR Team 2023-08-21, Execution NAMR Team 2023-09-04
    • 135

      Usually we'll only fetch active transaction history (via reading from config.transactions as a primary, but we have seen some cases where a service in the server can end up doing this briefly as a secondary when stepping down. This is fine conceptually since no writes will be able to occur once secondary, but it can cause this assertion to fail. Until we have a better solution for representing this state of being stepped down but not performing oplog application yet, we can just relax constraints for this read.

            Assignee:
            gregory.noma@mongodb.com Gregory Noma
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: