-
Notifications
You must be signed in to change notification settings - Fork 31
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
Investigate dividing Oracle procedure COLL_UPDATED_REPLICAS using virtual scope #548
Comments
To answer your question in chat, ATLAS uses scope more like we use campaign. So they have lots of different scopes. I don't know what we could do instead. Would we be able to segment on the first N characters of the LFN? Hash and mod 8 of the LFN? |
This is a good idea. The collection_replicas table for CMS has rucio datasets/CMS blocks. scopes and RSEs, but not campaign or LFN in it. CMS block names have something like |
@ericvaandering
|
I created the pull request for comments. |
I've dropped the priority of this as I believe the issue will become more or less mute with a future release of Rucio. Yuyi says the procedure is working well now. |
The problem:
The Oracle procedure runs every two minutes. The maximum number of rows in the table that the procedure can handle is about 40 million. However, when CMS has big data operations, such as massive deletion or data movement, the number of rows increased significantly in a short time, for example, we had 144+ m rows on June 28.
After talking about this in Rucio devl meeting. We learned that ALTAS is providing one single procedure into 8 different procedures simultaneously based on the data's scope.
So we will look into how CMS can improve our procedure.
The text was updated successfully, but these errors were encountered: