Increase transactionLifetimeLimitSeconds from 3 to 24 hours

XMLWordPrintableJSON

    • Fully Compatible
    • v4.0
    • Storage NYC 2019-03-25
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We should increase transactionLifetimeLimitSeconds from 3 to 24 hours for better build failure diagnostics when the task is kept alive by the logkeeper. In BF-12314, the transaction is timed out after the current 3 hour limit but did not get timed out after 2 hours because of network errors being printed in the task log. Increasing this to 24 hours would cause Evergreen to timeout the execution of the test.

            Assignee:
            Gregory Wlodarek
            Reporter:
            Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: