[SERVER-40233] Increase transactionLifetimeLimitSeconds from 3 to 24 hours Created: 20/Mar/19 Updated: 29/Oct/23 Resolved: 20/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.8, 4.1.10 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.0
|
||||||||
| Sprint: | Storage NYC 2019-03-25 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 26/Mar/19 ] |
|
Author: {'email': 'gregory.wlodarek@mongodb.com', 'name': 'Gregory Wlodarek', 'username': 'GWlodarek'}Message: (cherry picked from commit eb5136ad33e9821580843be0ac7b981a16cc30c5) |
| Comment by Githook User [ 20/Mar/19 ] |
|
Author: {'email': 'gregory.wlodarek@mongodb.com', 'name': 'Gregory Wlodarek', 'username': 'GWlodarek'}Message: |