Ensure crawler can't run out of space with --diskUtilization param #264
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #242
The first commit implements
--diskUtilization
as described in the issue. I found that this stopped a lot of crawls prematurely in local testing even though the total size, even after combining WARCs and generating WACZ, still wouldn't have crossed the disk threshold.The second commit modifies the routine to keep the disk utilization percentage high (90% by default) but instead projects whether that threshold is likely to be reached based on the size of the current archive directory (x4 if combineWARC and generateWACZ are passed, x2 if only one of them).