We have been working on the assumption that the recordings and located in the configured recording directory on the OpenVidu Pro server. By default, /opt/openvidu/recordings.
Would there be any issues if we mounted a S3 location using s3fs for the recordings location?
A related question, I see that there are also /opt/openvidu/recordings directories present on the media servers. The files are recorded on the media nodes and then copied to the OpenVidu node, how are the files managed on the media nodes? Do they need to be cleaned up?
You can test, but s3fs has several limitations and you probably have some performance issues with big files being modified in random locations.
Yes, the files are removed from media nodes automatically after downloading to master node.
It is in our roadmap to provide native s3 integration in OpenVidu PRO, so you can forget managing recordings. But there is no ETA.
Regards
Ok. I will try. We have noticed much better performance with Wasabi than S3 and the API is the same. We will test performance.
I see lots of (old) directories on the media nodes… are they deleted after transfer or via another method?
When adding S3 support, please allow custom S3 URI location so that S3 compatible services, like Wasabi, can be used.
We have used s3fs for a long time but the AWS Storage Gateway is a much more robust and reliable solution. It is easy to set up and operate.
@jcdmacleod, we just observed some information is still present in the media nodes when files are moved to master node. Definitely is a bug we have to fix.
@Thiago_Henrique thank you for recommend us AWS Storage Gateway. We will evaluate it when providing out of the box S3 recording for OpenVidu.
1 Like