Trying to understand how Jellysweep works

[cmerkle]

Hello, I got jellysweep up and running, but even after reading the docs I don't fully understand how it works. When a keep request is approved, what actually happens on the backend, and how do I look under the hood to make sure it's working? When a keep request is approved is the move kept forever, or is it as if it was just watched, and then after another 90 days or whatever? Will it eventually come back up in the dashboard to be re-requested? How does a keep request differ from "keep forever" on the admin keep or sweep page? Also the readme says that items are marked for deletion using radarr/sonar tags, but I only see tags applied when I "keep forever". Items marked for deletion or items with keep requests do not show any tags in the *arrs.

Ultimately what I'd like to do is ONLY start deleting things once I am running out of storage, and delete the oldest watched items first until I am below my storage threshold. Is this possible? I have my library paths setup but is there a way to verify that jellysweep is able to see remaining storage space? The GUI doesn't seem to show much, like space remaining, etc.

[jon4hz]

When you approve a keep request, jellysweep will ignore the item for 90 days (or whatever you configure as protection_period). If no one watches this item during this period, it will be picked up again by jellysweep in a new "cleanup cycle" - meaning that it will appear on the dashboard again where you can request to keep it once more.
If you watch the item during the protection period, it will loose it's protection status and jellysweep will pick it up again if the last_stream_threshold filter value applies.

How does a keep request differ from "keep forever" on the admin keep or sweep page?

As the name says, if you use the "keep forever" option it will be kept forever and never be picked up by jellysweep again.

Also the readme says that items are marked for deletion using radarr/sonar tags, but I only see tags applied when I "keep forever"

I just recently added a new database backend which replaces this tag based system, so the README is a bit outdated. The "keep forever" tag is still added in sonarr/radarr though, so that you can theoretically delete the database and those items will still be protected.

If you want to look under the hood, the database is probably a good point to start. By default, the database file is stored under ./data/jellysweep.db.

Ultimately what I'd like to do is ONLY start deleting things once I am running out of storage, and delete the oldest watched items first until I am below my storage threshold.

This isn't exactly supported right now. What you could do is set an insanely high cleanup_delay a then use disk_usage_thresholds with a lower max_cleanup_delay. This way your media would get marked for deletion, but only actually deleted if your disk usage exceeds the configure threshold. However, all your media that jellysweep marked for deletion would probably be deleted at once then. There is no option to make it stop deleting once your storage is below the threshold again.
To be honest, I wouldn't configure jellysweep like that, since it will make deletions more unpredictable.

I have my library paths setup but is there a way to verify that jellysweep is able to see remaining storage space?

If jellysweep couldn't read your storage usage, there would be errors in the logs.

The GUI doesn't seem to show much, like space remaining, etc.

Yeah, totally agree on that. But truth be told, I'm not a frontend developer so the UI is currently a bit of bare minimum only.

[cmerkle]

Thanks so much for the responses! This is great. It's a great project. I do really wish it could only delete the oldest watched media in order of last watch date or something only if hard drive space is low. Would you consider adding that feature if I submit a feature request? I don't really want to delete anything unless it gets to the point that I have to, and in that case I want what's deleted to be prioritized and delete as little as possible

[jon4hz]

Yes, please go ahead and create a feature request. I can't make you any promises but then I know at least that the demand is there ^^

[matteocnt92]

Hey @jon4hz, is there a way to remove or cancel a "keep" request from the UI? If I change my mind about keeping a specific movie, do I need to manually edit the database, or can I manage it from the dashboard?

[matteocnt92]

@jon4hz did you have time to look at my request? thank you