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

Bump transaction number on retry in retryable_writes_retry_without_internal_txns.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • 200

      This test currently retries a transaction statement on retriable and network errors, but always uses the same txnNumber. If the original failure is due to a failover, and the retry is sent to a new primary, mongos will not attach startTransaction to the request (because mongos does not clear the transaction participant list until commit or starting a new transaction), and so the new primary will attempt to continue the transaction and fail to do so.

            Assignee:
            kruti.shah@mongodb.com Kruti Shah
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: