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

Implement storage provider fallback for assets #1002

Closed
bedeho opened this issue Jul 17, 2021 · 1 comment · Fixed by #1017
Closed

Implement storage provider fallback for assets #1002

bedeho opened this issue Jul 17, 2021 · 1 comment · Fixed by #1017
Assignees
Labels
enhancement New feature or request tech

Comments

@bedeho
Copy link
Member

bedeho commented Jul 17, 2021

I am getting a substantial share of videos looking like this

Screenshot 2021-07-17 at 21 05 49

I was told by senior community people that the cause is that some storage providers are having trouble with all the new load, and they are re-synching with greater capacity (which apparently takes many days already!!), and Atlas does not deal properly with this.

Could we instead introduce some behaviour where Atlas tries another storage provider if there is a failure?

@bedeho bedeho added the enhancement New feature or request label Jul 17, 2021
@bedeho bedeho changed the title Greaceful playback failure Graceful playback failure Jul 17, 2021
@bedeho
Copy link
Member Author

bedeho commented Jul 19, 2021

It turns out that there is no retry behavior for any asset, lets introduce that as a backstop for something not working properly in the infra.

@kdembler kdembler changed the title Graceful playback failure Implement storage provider fallback for assets Jul 19, 2021
@kdembler kdembler added the tech label Jul 19, 2021
@kdembler kdembler self-assigned this Jul 19, 2021
@kdembler kdembler added this to the Misc tech tweaks milestone Jul 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request tech
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants