-
Notifications
You must be signed in to change notification settings - Fork 618
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
Stream stuck in broadcasting state when one of the node cluster gets inaccessible #5361
Comments
This might be related as well. I am on Enterprise Edition 2.6.2 20230623_0843 Screen.Recording.2023-07-22.at.11.02.04.PM.mov |
This could be connected to a web panel attempting to send a request to a node that lacks the stream. Addressing this by directing requests to the appropriate cluster nodes can resolve the issue. Further information will be provided shortly. |
Please check mentioned PR for fix and bug explanation. |
I updated to 2.6.3 but I still have 2 streams stuck in the broadcasting state that I am unable to stop or delete |
Hi @SebastienGautier, You can send it to support@antmedia.io |
Hi @mekya |
Hi @SebastienGautier , So how shall we proceed? If you want to speed up the process, you can send an email to support@antmedia.io |
Short description
In a scenario where there are two nodes in the cluster and client is publishing RTMP stream to one of the node and that node gets inaccessible then the streams will be stuck in broadcasting mode.then we cannot delete that stream as well they are just stuck.
Environment
Steps to reproduce
Expected behavior
streams should be offline
Actual behavior
streams stuck in broadcasting
When I check the broadcast object using REST API.
the origin IP of the broadcast is the node which was disconnected.
Logs
Place logs on pastebin or elsewhere and put links here
Ask your questions on Ant Media Github Discussions
The text was updated successfully, but these errors were encountered: