As I understand from other issues here, that can happen when using NFS (slow) storage. I using NFS, because I have no other option, but the NFS Server runs on a dedicated host and Peertube runs as a VM on that same host. In normal situations that setup runs very smooth, without issues.
Describe the solution you would like
For Object Storage there is an option, that after transcoding the files are moved to the new storage. How about a similar function for live streaming. That we can have a separate storage path for live streaming, like: /var/www/peertube/storage/live/, and when the live stream stops and the stream got prepared for VOD it moves to the default location /var/www/peertube/storage/streaming-playlists/.
That would make it possible to use a smaller and faster storage for live straming and a bigger and slower storage for VOD. Even a Ram Disk could be possible for that use case.
Describe the problem to be solved
When I test the live streaming function, one time peertube crashes and restart and I get that errors:
As I understand from other issues here, that can happen when using NFS (slow) storage. I using NFS, because I have no other option, but the NFS Server runs on a dedicated host and Peertube runs as a VM on that same host. In normal situations that setup runs very smooth, without issues.
Describe the solution you would like
For Object Storage there is an option, that after transcoding the files are moved to the new storage. How about a similar function for live streaming. That we can have a separate storage path for live streaming, like: /var/www/peertube/storage/live/, and when the live stream stops and the stream got prepared for VOD it moves to the default location /var/www/peertube/storage/streaming-playlists/.
That would make it possible to use a smaller and faster storage for live straming and a bigger and slower storage for VOD. Even a Ram Disk could be possible for that use case.