[SERVER-57564] Increase system timeout duration to >2 hours to allow fio to copy over all files Created: 25/Mar/21 Updated: 29/Oct/23 Resolved: 10/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.15, 4.4.7, 4.0.26, 5.0.0-rc2, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vlad Rachev (Inactive) | Assignee: | Mikhail Shchatko |
| 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: |
v5.0, v4.4, v4.2, v4.0
|
||||||||
| Sprint: | STM 2021-06-14 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
david.daly
We might not be able to change fio's runtime, since it needs to copy over the snapshot data. Let's instead look to increase the timeout to give it more time to finish this.
|
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 11/Jun/21 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: (cherry picked from commit c970224e10642c7155ffca8c698d40848481c54e) |
| Comment by Githook User [ 10/Jun/21 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: (cherry picked from commit c970224e10642c7155ffca8c698d40848481c54e) |
| Comment by Githook User [ 10/Jun/21 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: (cherry picked from commit c970224e10642c7155ffca8c698d40848481c54e) |
| Comment by Githook User [ 09/Jun/21 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: (cherry picked from commit c970224e10642c7155ffca8c698d40848481c54e) |
| Comment by Githook User [ 09/Jun/21 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: |
| Comment by Brooke Miller [ 06/Apr/21 ] |
|
We discussed that we'll increase the exec_timeout_secs to be the same as the task timeout. We'll likely also need to increase the DSI timeout, too. |
| Comment by Vlad Rachev (Inactive) [ 25/Mar/21 ] |
|
Yes it's logkeeper specific. Ok I see. In that case we should look into increasing some timeout. A successful logkeeper takes around 7-8 hours, so we should be able to make this not time out after 2 hours (though evergreen timeouts are hard to grok). I will change the ticket title to reflect this and reassign to STM to figure out the timeout. |
| Comment by David Daly [ 25/Mar/21 ] |
|
vlad.rachev this is logkeeper specific, yes? We can take a look. We might not be able to speed it up. This is an important step when working with an AWS snapshot. It forces the system to copy over all the data to the local system, which is required for this test. |