Update wmcore_transferor global and local quotas dynamically #914
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.
Currently, wmcore_transferor quotas are statically set and it's as follows [1]. Its usage reached to record high of 44.4 PB [2] and made many sites run out of space. In this issue [3], we discussed a strategy to introduce global and local limits for this account to keep its usage under control. This PR implements what's been discussed in that issue as well as my additions. To explain the changes:
The output of a dry-run can be found at [4]
Before Eric reviews it, I'd like to get Ops' and WM's feedback. That's why I'll mark the PR as draft for now. Once we agree that the PR reflects what we need, I'll open the PR for Eric's review. Let me tag @Panos512 @hassan11196 @drkovalskyi @amaltaro @eachristgr and @juanpablosalas
[1]
[2] https://monit-grafana.cern.ch/d/viS0q0ZSz/rucio-account-monitoring?orgId=11&from=now-90d&to=now&var-RSE=All&var-RSEType=DISK&var-AccountName=wmcore_transferor&var-AccountType=All
[3] https://its.cern.ch/jira/browse/CMSTRANSF-479
[4]