[SERVER-44843] Increase the max size of core dump tarballs uploaded to S3 from 5GB to 10GB Created: 26/Nov/19 Updated: 29/Oct/23 Resolved: 19/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Raiden Worley (Inactive) | Assignee: | Raiden Worley (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-hanganalyzer | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | STM 2019-12-26 | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Comments |
| Comment by Raiden Worley (Inactive) [ 20/Dec/19 ] |
|
We went ahead and closed this because the limit for core dumps is already 10GB. The configuration for resmoke only limits the size of archived data files, not core dumps. And Evergreen's invocation of the hang analyzer uses its default limit of 10GB for core dumps. |