You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My space usage doesn't appear to be updating while the instance is downloading videos for redundancy. My concern is that this could cause the instance to download more then the space set/allocated for redundancy, causing potential issues, such as additional fees from the storage provider.
If all jobs are stopped and the instance is not downloading videos (and perhaps it's a hard restart) the space usage will update.
Steps to reproduce
Manually queue videos for download on redundancy
Describe the expected behavior
Space is updated after every video is downloaded.
Additional information
PeerTube instance:
URL: vidbin.org
Version: 6.0.3
NodeJS version: 20.11.0
Ffmpeg version: git
The text was updated successfully, but these errors were encountered:
Actually, I'm not sure if manual videos count at all towards the space usage. That being said my concern is that this may translate over to the automated system as well.
Actually, I'm not sure if manual videos count at all towards the space usage. That being said my concern is that this may translate over to the automated system as well.
I was correct, it doesn't update the space when using the automated redundancy options until you restart the instance.
Describe the current behavior
My space usage doesn't appear to be updating while the instance is downloading videos for redundancy. My concern is that this could cause the instance to download more then the space set/allocated for redundancy, causing potential issues, such as additional fees from the storage provider.
If all jobs are stopped and the instance is not downloading videos (and perhaps it's a hard restart) the space usage will update.
Steps to reproduce
Describe the expected behavior
Space is updated after every video is downloaded.
Additional information
The text was updated successfully, but these errors were encountered: