Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(cloud): Retry on all failures #165

Merged
merged 1 commit into from
Oct 25, 2024

Conversation

joeyparrish
Copy link
Member

Uses basic retry settings for GCS and S3.

If we do not pass these params, GCS would normally only retry if certain params were passed so that it knew the operation was definitely idempotent. We know our use case, so we know we can safely retry.

There will never be two versions of the same segment file, or two concurrent writes to the MPD, for example. So both uploads and deletes can be safely retried.

Uses basic retry settings for GCS and S3.  If we do not pass these params, GCS would normally only retry if certain params were passed to convince it that the operation was idempotent.  We know our use case, so we know we can safely retry.  There will never be two versions of the same segment file, or two concurrent writes to the MPD, for example.
@joeyparrish
Copy link
Member Author

Still verifying this fix. It takes a long time for these failures to show up, but they were being treated as fatal before.

@joeyparrish
Copy link
Member Author

This appears to be working. I hadn't made it past 6 hours with the previous revision, and we just reached 7.5 without errors with this one.

@joeyparrish
Copy link
Member Author

This is definitely working. In combination with some other changes, also in Packager, I've made it through several loops in my live stream now without errors. It has been running for the last 13.5 hours. I think with this, we have the most stable and performant cloud upload feature we've ever had.

@joeyparrish joeyparrish merged commit 7bb46d4 into shaka-project:main Oct 25, 2024
2 checks passed
@joeyparrish joeyparrish deleted the cloud-retry branch October 25, 2024 20:22
@github-actions github-actions bot added the status: archived Archived and locked; will not be updated label Dec 24, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: archived Archived and locked; will not be updated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants