You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
There are other LPMS transcode errors not in the exported LPMSErrors map that are not currently marked as non-retryable. As a result, when B encounters these errors from O it'll retry the segment even though the segments cannot be transcoded.
Perhaps it'd make sense to just treat all errors that come from LPMS as non-retryable instead of trying to enumerate all of them. This may be too extreme though - should think about whether there are cases where the errors from LPMS should be retryable.
The text was updated successfully, but these errors were encountered:
We should keep in mind that there are certain LPMS errors that we should probably retry on. For example, if an OOM error is returned, that segment could still be transcoded by another node.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
There are other LPMS transcode errors not in the exported LPMSErrors map that are not currently marked as non-retryable. As a result, when B encounters these errors from O it'll retry the segment even though the segments cannot be transcoded.
Ex.
Invalid argument
Perhaps it'd make sense to just treat all errors that come from LPMS as non-retryable instead of trying to enumerate all of them. This may be too extreme though - should think about whether there are cases where the errors from LPMS should be retryable.
The text was updated successfully, but these errors were encountered: