-
Notifications
You must be signed in to change notification settings - Fork 106
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
Support partial data placement/location for PREMIX pileup #11537
Comments
This is likely a meta-issue and we need to think and create more manageable/actionable issues. |
hi @amaltaro
Does this document contain any sensitive data? At least to me, it seems not to be the case. If @drkovalskyi does not object, I am in favor of linking it in the issue here. Because this document does contain important information and is a major pointer to the issue and how we currently handle pileup data. |
As we only have one enhancement issue opened against this project, and the full functionality has been implemented and deployed to production, I think we can declare this project as completed. Thank you very much Valentin for carrying over most of this development, and everyone else that helped with discussions/suggestions and so on. Closing this one out. |
Impact of the new feature
MSPileup (but will require changes at Global WorkQueue and WMAgent)
Is your feature request related to a problem? Please describe.
This topic has been discussed a few times already and Dima also started gathering the feature requirements in a google document named "Premix data management for Production", which I won't link here to avoid unwanted access.
The main goal is to keep a fraction of a PREMIX container in the storage, being able to shrink or expand it as needed.
Further details and WMCore dependencies are still to be discussed and investigated.
In a private chat with Hasan today, he also expressed that this is the most important issue for P&R, once MSPileup is deployed and fully functional in production.
Describe the solution you'd like
The expected solution is as follows:
The original requirements described in the document say:
"""
"""
Sub-tasks for this meta-issue are:
Extra sub-tasks created along the way:
Not a sub-task but potentially related: WMAgent: refactor pileup json location in the sandbox #11735
Describe alternatives you've considered
Keep placing and enforcing the whole container to be available at any given RSE.
Update from a discussion in the weekly O&C meeting:
Additional context
It requires further investigation, but I do think that in order to support this, we should also support live update to the pileup JSON map that is shipped with every single job. In other words, we cannot create a pileup location JSON file at the beginning of the workflow and keep using it - unchanged - during the lifetime of a workflow.
The text was updated successfully, but these errors were encountered: