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

Fix snapshot_read_kill_operations.js to handle read-only transactions that are aborted

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.1.12
    • Sharding
    • Fully Compatible
    • ALL
    • Sharding 2019-05-20
    • 13

    Description

      It turns out that for read-only transactions, it is allowable that one shard commit and one shard abort, as long as the client receives an error (since "committing" for a read-only transaction doesn't do anything except wait for the data read to be majority committed). In this case, a read-only transaction was interrupted, causing one shard to commit and the other to abort. The test should be fixed to handle this case.

      Attachments

        Issue Links

          Activity

            People

              esha.maharishi@mongodb.com Esha Maharishi (Inactive)
              matthew.saltz@mongodb.com Matthew Saltz (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: