Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redundancy - Space usage not updating #6239

Open
vid-bin opened this issue Feb 22, 2024 · 3 comments
Open

Redundancy - Space usage not updating #6239

vid-bin opened this issue Feb 22, 2024 · 3 comments

Comments

@vid-bin
Copy link

vid-bin commented Feb 22, 2024

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.

Screenshot 2024-02-21 at 4 01 50 PM

Steps to reproduce

  1. 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
@vid-bin
Copy link
Author

vid-bin commented Feb 22, 2024

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.

@vid-bin
Copy link
Author

vid-bin commented Feb 22, 2024

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.

@Chocobozzz
Copy link
Owner

Hi,

Redundancy stats are cached on server side. I think we can add a custom route/bypass to disable cache for this specific page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants