-
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
access time should be updated on additional events #200
Comments
I think maybe trim should not update access time. We should also put touch in the list of APIs which should be added. |
Is there a plan to release an update as 2.7.1 to address this, and if so do you have an ETA? Also, could the documentation for the plugin be updated to show which PEP's trigger it please? cheers John |
Are there plan's to implement this for: if I do:
The needed AVU is not set. What needs to be changed to get it to work for |
Yes, I think that we just need to add these PEPs to the big irods_capability_storage_tiering/libirods_rule_engine_plugin-unified_storage_tiering.cpp Line 243 in 67a2185
|
Updated code with a debug statement:
So it shows whith which pep it entered Did a small test with irsync between two zones (from iRODS 4.2.12 to 4.3.1):
The logfile shows that it entered with:
It should have updated the AVU if it matches:
Will test some more. |
There's also |
For 2.7.0, this code determines when access time is applied:
https://github.com/irods/irods_capability_storage_tiering/blob/2.7.0/libirods_rule_engine_plugin-storage_tiering.cpp#L74
For 2.7.0, I see:
Which suggests we also need to handle:
The text was updated successfully, but these errors were encountered: