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

Add non-transactional afterClusterTime find to multi_statement_transaction_atomicity_isolation.js

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Repl 2019-05-20, Repl 2019-06-03

      Description

      afterClusterTime finds don't get killed automatically on stepdown or stepup. To make sure we don't deadlock, adding another state that just runs an afterClusterTime find would be useful. I'm not sure if there are any consistency checks we can add as well or anything we can expect from what the find returns, but just running the command may weed out deadlocks involving prepare conflicts outside of transactions.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              judah.schvimer Judah Schvimer
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: