-
-
Notifications
You must be signed in to change notification settings - Fork 546
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
Chunks show encoding a Fail status, but not any apparent problems #929
Comments
Aha, caught one in the act. From the Celery log:
|
I'm wondering at this point if maybe there are somehow two concurrent |
It is most definitely running multiple instances of
|
Need to do some more debugging, but from reading through the code I think this assumption is not true: Line 1457 in c5047d8
|
So, I think what's happening is that a chunk gets to this point: Line 1493 in c5047d8
If the disk throughput is low or the video is very long, there is nothing preventing another encoding |
It's possible that by changing these check loops: Line 1475 in c5047d8
Line 1480 in c5047d8
To check to make sure that each chunk is in a "success" state instead of just making sure that it has media, it should make it so it's not able to do concurrent combines. |
Describe the issue
Often times when transcoding to an MP4 profile one of the chunks of an encoding will come back as an encoding fail but the video seems to play fine if I pull the actual encoded file. The logs don't show any errors and look the same as successful chunks,
Retries
is0
,Status
isFail
, andTotal run time
is also0
. But then if I click onEncoding file
it plays just fine and everything looks okay. I also never see this with VP9 encoding.To Reproduce
I'm not sure how to reproduce this. However, I did not see this problem until I moved to a server setup with much higher capacity but also higher disk latency. I've raised the timeouts for Celery to allow each task to run for considerably longer, far longer than successful chunks take to encode, but the issue persists.
Expected behavior
I would expect that the chunk, which from everything I'm seeing did in fact succeed in encoding, would be marked as
Success
instead. What I find most odd is thatTotal run time
is0
- seems like even for a failure, that should be filled in with some kind of a value.Screenshots
Can't share screenshots of this setup unfortunately.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: