HOTFIX: Allow the mastodon copy to fail for taking too long #64
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.
We're seeing an issue where files >30GB will fail on the
S3CopyObjectOperator
with the following exception:Ultimately we'll need to change the botocore timeout config to be able to increase the timeout (like this post suggests). Until I get a chance to do that though, this will allow the cleanup tasks to run if the copy step fails. Previously, with the copy step failing, the backups would continue accumulating and take up more space (and money). This is a temporary workaround to make sure we aren't incurring extra costs.