-
Notifications
You must be signed in to change notification settings - Fork 178
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
Transcoding session ended by the Broadcaster when no sessions were transcoded #2755
Comments
I think they are related to this PR: #2685, so it's just an additional debug log message. Closing, feel free to reopen if this log causes any issues. |
What I don't understand is why is there a message stating that Transcoding session ended by the Broadcaster when there isn't a session to end? The original request was to have better error reporting that explained why a session ended. Are these messages that a Broadcaster did not choose the O for the job during discovery and is therefore ending the session? If that's the case a better message would be Orchestrator not chosen during discovery to receive session by Broadcaster or something along those lines. |
@mjh1 Any thoughts on that? |
Ah yep the logging change definitely isn't behaving as expected. I have a feeling I know what's happening, I have tried to reproduce locally with no luck though. I'll update when I know more. |
This should be fixed now, we tested on some live Orchestrators to verify it. |
Since the update to 0.5.37 Os have been receiving Transcoding session ended by the Broadcaster messages in their logs even when no sessions have been transcoded. They don't appear to cause any issues but several of us are wondering what they mean.
Below is a log from one of my Os that hadn't had a session in over 30 mins.
The text was updated successfully, but these errors were encountered: