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

Prevent dbVersion refreshes from failing transactions in txn_recover_decision_using_recovery_router.js

    • Fully Compatible
    • ALL
    • v5.0, v4.4, v4.2
    • Sharding 2022-02-21, Sharding 2022-03-07, Sharding NYC 2022-03-21
    • 33
    • 1

      txn_recover_decision_using_recovery_router.js runs transactions without transient error retry logic. If a database version refresh is triggered concurrently with a transaction, the transaction can reach the 5ms lock timeout waiting for an IX database lock and fail with a transient error. The test should be modified to not fail because of this, either by adding retry logic or forcing shards to refresh their database version earlier when no transactions are running.

            Assignee:
            israel.hsu@mongodb.com Israel Hsu
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: