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
Alternate BaseURL failover broken #1702
Comments
I think we have a fix which could be PR'ed tomorrow after some internal review. |
the Replacement queue was put in for fast switching in May. Can we not invoke the scheduler method outside of the timer based on some failover signal or error? |
Pretty much, yes. Needed a further tweak to ensure initialisation segments were handled correctly. |
Fix #1702 - ensure replacements are rerequested on failure
It looks like 636f4f9 has broken BaseURL failover.
This appears to be because the scheduler is not running when a failure occurs, and this is required in order to re-request segments from an alternative BaseURL. It used to be the case that replacement requests were downloaded immediately but this seems to have been replaced with a queue which is serviced by a scheduler.
More as we have it.
#1701 is also required.
The text was updated successfully, but these errors were encountered: