-
Notifications
You must be signed in to change notification settings - Fork 10
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
implement trimming of objects in tier0 resource when preserve_replicas is set to true #253
Comments
What should happen if there are three or more tiers? Would your sentence read ... 'all tiers'? |
So this policy would remove the oldest duplicated files, in order, if they are larger than a certain size, and until a threshold value is met? Policy for the ordering could be customizable - or just part of an enum... ['oldest', 'largest', 'smallest'] |
I would say if it is in more than one tier. |
For now my rule as implemented just does following:
|
Got it. But a 'minimum filesize to trim' might also be a handy knob to have. |
FEATURE REQUEST
VERSIONS
iRODS 4.3.1
proposed BEHAVIOUR
A system with tier 0 and tier 1.
The parameter
irods::storage_tiering::preserve_replicas
is set to true for all tiers.A new parameter
irods::storage_tiering::preserve_replicas_size
is set to the number of bytes to keep on tier0When the storage tiering rule fires of it also checks for the object size in the tier0.
If it is too much it trims files based on date (oldest first) till it reaches the limit. This might also be configarable like the query to find files to migrate.
It only does it for files which are in both tiers.
During the operation it also updates the attribute
irods::storage_tiering::group
with a new unit if it is neededAn example of how we now implement it in a python iRODS rule
The text was updated successfully, but these errors were encountered: