High disk usage when doing RTSP to WebRTC

[Andreas]

Hi! We have 5 live streams running with RTSP to WebRTC, and sometimes, just sometimes, disk usage goes up by multiple gigabytes each hour. Recording is not enabled.

To fix this, we needed to stop all the streams, and manually delete all transport stream files. (We saw up to 700k of these files in the WebRTC/streams folder)

One other problem we are seeing; If a recording is running and the disk fills completely up, the AMS stops and refuses to start again until we manually delete the VODs from the server.

 

Are there anyone else that has encountered the same things, and know a fix for it?

 

 

Edited December 5, 2022 by Andreas
Irrelevant for question

[Yash]

Hi @Andreas
After our discussion on the Support ticket. Let me put my answer here as well:

1. It seems all the HLS files are stored on the server. It was a known bug in v2.4.3. Please check out the below link for an explanation of this issue and a workaround solution.
https://github.com/ant-media/Ant-Media-Server/issues/4196

 

For a permanent solution, I recommend that you upgrade your server to the latest version, 2.5.1. Please follow the below document to upgrade your server.
https://resources.antmedia.io/docs/upgrade-ams
 

2. Yes, it is an expected behavior. If the recording is ongoing, the tmp extension file will take up space on the server's local disk until the recording is completed. For the solution of this problem, you may mount an extra storage device to the streams directory of the Ant Media server. Another option is to use S3 Fuse to map your stream directory to cloud storage (an S3 bucket). Kindly check out the following link:
https://stackoverflow.com/questions/72670843/how-to-record-hls-streamsto-s3-in-ant-media-server