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

Improve error code for checking lastCommittedOpTime in TransactionParticipant

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Replication

    Description

      Currently, we throw InvalidOptions when checking the lastCommittedOpTime for a commitTransaction command. While this isn't necessarily a bug for proper usage of two phase commit (since we ignore this error and auto retry in the transaction coordinator), in testing it is possible that we run a commitTransaction before the lastCommittedOpTime has been recovered (BF-25428). This ticket is to track/discuss whether or not the error code should instead be a retryable one. 

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            jason.zhang@mongodb.com Jason Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: