-
Notifications
You must be signed in to change notification settings - Fork 176
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
[8.0] TransformationCleaningAgent: add Clean With RMS option #7223
Conversation
…quests instead of direct cleanup
45e7f59
to
814ecea
Compare
@@ -387,6 +395,11 @@ def cleanContent(self, directory): | |||
# Executing with shifter proxy | |||
gConfigurationData.setOptionInCFG("/DIRAC/Security/UseServerCertificate", "false") | |||
failed = {} | |||
if self.cleanWithRMS: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So actually this branch (i.e., cleanContent function) is never used for me, because everything is based on meta data to find files and not on directories
Do you think the flag could be removed from v8.1? (and the |
Fine for me, I just thought maybe some people only have the TS but not the RMS set up so we don't mix the two systems by default, or this is considered not safe enough. |
RMS is necessary, an installation can't live without it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for that !
Sweep summary Sweep ran in https://github.com/DIRACGrid/DIRAC/actions/runs/6484826852 Successful:
|
So this was implemented some time ago, when a transformation with >10k files had to be cleaned. I am not sure I exercise this logic too often...
It is completely optional, so I think OK for 8.0.
It might be a bit loose on the error handling side, which is probably why I kept it in my hot fixes branch...
It request submission is successful, the transformation is marked as cleaned.
It is not waiting for requests to succeed, if something fails one can always clean a transformation again.
So review away.
BEGINRELEASENOTES
*TS
NEW: TransformationCleaningAgent: add CleanWithRMS option to clean files via the RequestManagementSystem asynchronously rather than serially in the agent run itself
ENDRELEASENOTES