ant-media / Ant-Media-Server

Ant Media Server is a live streaming engine software that provides adaptive, ultra low latency streaming by using WebRTC technology with ~0.5 seconds latency. Ant Media Server is auto-scalable and it can run on-premise or on-cloud.
https://antmedia.io
Other
4.27k stars 628 forks source link

GCS Integration Issue - MCU & Recording #4619

Open akiziltoprak opened 1 year ago

akiziltoprak commented 1 year ago
  1. GCS Integration Issue with MCU: The stream recording to GCS causes the issue with the MCU feature of Ant Media Server.
  2. GCS bucket video upload: Current stream records saves the video and other files to GCS after we end the broadcasting. But the requirement here is that the HLS output files should be uploaded during the live broadcast itself, not after the broadcast is stopped.
akiziltoprak commented 1 year ago
  1. We need to implement the streaming solution using GCP CDN as explained in the doc here. For this, we need to store the HLS output stream in GCS bucket and then stream it via CDN. But now AFAIK the video output appears in the GCS bucket after the broadcast has been stopped. But the requirement here is that the HLS output files should be uploaded during the live broadcast itself not after the broadcast is stopped.
mekya commented 1 year ago

I don't understand What's problem is for GCS Integration Issue with MCU:?

Could you please write the reproduce scenario or explain further?

Steps

  1. ...
  2. ...
  3. ...

Actual behaviour: ... Expected behaviour: ...

For the second issue, it's likely that fuse adaptor resolves that issue.

akiziltoprak commented 1 year ago

Steps to reproduce the issue are as below:

  1. Deploy the AMS on GKE.
  2. Add the Adaptive bitrate feature for MCU and test the MCU feature.
  3. Next do the necessary changes for the GCS integration and test the GCS feature functionality for normal broadcasting without MCU.
  4. Now try the MCU feature and try publishing. You will get a PublishTimeOut error and might also see the origin pods crashing in the GKE setup.
mekya commented 1 year ago

@muratugureminoglu , how did you resolve the publishTimeout issue in here? https://github.com/ant-media/Ant-Media-Server/issues/4054 It's likely the same issue.

If the origin pods are crashing, shall we get the log files under /usr/local/antmedia/log directory and any file with hs_err_pidXXX*.log under /usr/local/antmedia?

PS: I'm just trying to understand and simplify the resolution process

SelimEmre commented 1 year ago

Hi guys,

Let me give you some details regarding this issue. We just set some meetings with this guy who is encountering this issue. It seems that this issue was related to the DNS policy configuration. They just changed to ClusterFirstWithHostNet and used the TURN server in their environment. They reported that this issue was resolved. Just wanted to update here.

Best Regards, Selim

muratugureminoglu commented 1 year ago

We already using the ClusterFirstWithHostNet DNS policy option in our official YAML files[1].

[1] https://github.com/ant-media/Scripts/blob/master/kubernetes/ams-with-turn-server/ams-k8s-deployment-origin.yaml#L27