Automatic cleaning of input data Rucio rules #12427
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Jenkins results:
|
nhduongvn
force-pushed
the
data_carousel
branch
from
57a8335 to
78443bc
Compare
|
Jenkins results:
|
Collaborator
Author
|
These are failed unit tests which not related to the new codes: |
Collaborator
Author
|
please test |
|
Jenkins results:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #11409
Status
not-tested
Description
To automatically deleting the Rucio rules of input data set (block) of workflows, we implement a cherrypy thread that periodically scans the global workqueue for completed workqueue elements (
percentSuccess == 100 and percentComplete == 100) and deletes the corresponding Rucio rules of input data blockThere are also similar implementations in MSRuleCleaner (a new Pline for cleaning). However, Alan pointed out that MSRuleCleaner only runs on workflows at "later" stages ("announced"?). Therefore, the cleaning will not be done as soon as the processing of input data is complete. The code is still kept here (maybe for proof-of-concept for a new MS?).
Is it backward compatible (if not, which system it affects?)
YES
External dependencies / deployment changes
Yes, it requires the settings/configurations for a cherryPy thread that point to the Rucio account of input data set rules and the global queue