Skip to content
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

Merged
merged 1 commit into from
Oct 11, 2023

Conversation

andresailer
Copy link
Contributor

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

@DIRACGridBot DIRACGridBot added the alsoTargeting:integration Cherry pick this PR to integration after merge label Sep 28, 2023
@@ -387,6 +395,11 @@ def cleanContent(self, directory):
# Executing with shifter proxy
gConfigurationData.setOptionInCFG("/DIRAC/Security/UseServerCertificate", "false")
failed = {}
if self.cleanWithRMS:
Copy link
Contributor Author

@andresailer andresailer Sep 28, 2023

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

@andresailer andresailer linked an issue Sep 28, 2023 that may be closed by this pull request
@fstagni
Copy link
Contributor

fstagni commented Sep 29, 2023

Do you think the flag could be removed from v8.1? (and the if-else with it)

@andresailer
Copy link
Contributor Author

Do you think the flag could be removed from v8.1? (and the if-else with it)

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.

@fstagni
Copy link
Contributor

fstagni commented Sep 29, 2023

RMS is necessary, an installation can't live without it.

Copy link
Contributor

@chaen chaen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for that !

@fstagni fstagni merged commit 165a6a5 into DIRACGrid:rel-v8r0 Oct 11, 2023
20 checks passed
@DIRACGridBot DIRACGridBot added the sweep:done All sweeping actions have been done for this PR label Oct 11, 2023
DIRACGridBot pushed a commit to DIRACGridBot/DIRAC that referenced this pull request Oct 11, 2023
@DIRACGridBot
Copy link

Sweep summary

Sweep ran in https://github.com/DIRACGrid/DIRAC/actions/runs/6484826852

Successful:

  • integration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alsoTargeting:integration Cherry pick this PR to integration after merge sweep:done All sweeping actions have been done for this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TransformationCleaningAgent should use the RMS
4 participants