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

Non hermitic test commit_prepared_transaction_errors.js should retry

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • 5.3.0, 5.0.5, 5.1.1
    • None
    • ALL
    • 19

    Description

      As mentioned in referenced BF is experiencing the very rare race when `WiredTigerIdIndex::_insert()` failed with WriteConflict error. The failure happens approximately once per month and only on in-memory fixtures. The WriteConflict is not expected, however it's legal, there is no consistency error and the error message clearly says: "Please retry your operation or multi-document transaction."

      Most likely, the cause of this failure is non-hermetic test rather than a real bug. The action taken should not change the strength of the test correction and should verify that the race is brief and not persistent.

      What we need to verify is that the test should pass after a short retry, we must ensure that the retry succeeds and the WriteConflict is transient. I think it's better to retry just the failed test case instead of the whole suite.

      Attachments

        Activity

          People

            lamont.nelson@mongodb.com Lamont Nelson
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: