-
Notifications
You must be signed in to change notification settings - Fork 110
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
bc_clean_old_dirs also cleanup db files #3860
Comments
These files do get cleaned up after so long (7 days after it's completed is the default). Maybe it's a case of backward comparability? Like we started to clean these files, but never cleaned the files from previous versions? |
@johrstrom that's possible. the old files i found were from our 2.0.X setup (and over 9 months old); but that means they were also not cleaned up by 2.0 (not sure when the cleanup was added). anyway, i will try to cleanup as much as possible; and will reopen this when i see files from 3.1 era not being cleaned up. |
To be clear - here's the logic to delete them if they're old. I feel like it was added in 2.0, but would have to check to be sure.
It would seem that ondemand/apps/dashboard/app/models/batch_connect/session.rb Lines 200 to 206 in de41471
|
bc_clean_old_dirs now cleans up session output dirs that are certain age; but can it be extended to cleanup also files in the db dir, eg
~/ondemand/data/sys/dashboard/batch_connect/db
? we have some users who have files there that are very very old, and reference clusters that are no longer around. afaik, these files are one per job; so shouldn't be older then max job age (but we are fine if they are cleaned eg together with the bc_clean_old_dirs logicThe text was updated successfully, but these errors were encountered: