-
Notifications
You must be signed in to change notification settings - Fork 68
Extend express ALCARECOs lifetime on disk to 1 year #4766
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
Conversation
|
We need an estimate of how much data we are talking about. Based on that we can decide if it's Ok to make a year long subscription. In general, please keep in mind that Tier0 subscriptions are meant to be used as initial subscription, i.e. if user's needs go beyond what T0 rules are providing new Rucio rules should be created by the user. |
|
Hi Dima,
Ok we'll try to get an estimate asap!
This is not always true for the express case, since there is not default tape subscription, once the 3 months are over the dataset is deleted for good. E.g. this happened now with: |
|
Can you clarify why 3 months is not enough to realize that you need the data for longer and you need to make a new subscription? Is it because the data is used only much later? Maybe we should reconsider the idea of having a tape copy? Basically we should not put all data on disk for a year if we just need a small fraction once in a while. |
|
Hi @drkovalskyi
For example the StreamExpressAlignment alcareco I mentioned in my previous message is used to derive the beamspot conditions for the re-reco, so maybe 1 year is an overshoot, but at the same time 3 months is too short...
Yes I guess this enters in the same general discussion about alcareco handling (see also https://its.cern.ch/jira/browse/CMSTZ-1005)
Are you now referring to T2_CH_CERN or Disk sites in general? |
|
Ok, so we are talking about ~35TB for ~20-25% of data, i.e. it's 100-200TB per year. I think it's small enough to just keep it all for a year. |
|
Thanks Dima! @germanfgv @jhonatanamado I guess this PR can be merged then. |
|
test syntax please |
Config Change Request
Not really a replay request, more just a config change.
Proposed Changes
In #4642 a lifetime of 3 months was added to the express alcarecos. Since this means that when such lifetime expires these datasets (which are not custodial as the prompt ones) get deleted (not transferred to tape), we propose to increase the lifetime to 12 month so that they can be used, for example, for the derivation fo the re-reco conditions.
In this PR I increased the lifetime for:
@drkovalskyi given your comment in #4642 (comment) any feedback on this proposal is welcome (including possibly setting different
diskNodes for storing these alcarecos).T0 Operations cmsTalk thread
https://cms-talk.web.cern.ch/t/config-change-for-keeping-express-alcareco-on-disk-for-1-year/15927