Modify FLE2 no_passthrough tests to make considerations for maxRetries of internal transactions

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Security 2022-05-30
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently tests such as fle2_contention_delete.js, intentionally introduce a write contention that cause internal transactions to get back a retryableWriteError. With the introduction of SERVER-59566, capping the number of retries for an internal transaction can make the tests flaky since those tests can easily exceed the max retries depending on the machine the test is provisioned on (i.e. slow machine issues).

            Assignee:
            Erwin Pe
            Reporter:
            Jason Zhang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: