We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The archive metadata plugin sends empty collocation hints to FTS.
The following have been observed in ATLAS and CMS FTS databases for multiple transfers:
MySQL [newfts3atlas]> select archive_metadata, count(*) from t_file group by archive_metadata; +---------------------------+----------+ | archive_metadata | count(*) | +---------------------------+----------+ | NULL | 15780 | | {"collocation_hints": {}} | 14437895 | +---------------------------+----------+ 2 rows in set (29.215 sec) MySQL [newfts3atlas]
I think it could be a side effect that when no policy is configured, the default is to send an empty dict?
If there are no collocation hints, the archive metadata should not be sent.
Observed in production env
No response
The text was updated successfully, but these errors were encountered:
Transfers: Ensure no archive metadata is used if a plugin is not conf…
2b81a80
…igured rucio#6780
21d973f
c86c488
…igured #6780
bbb0287
Thanks @voetberg !
Sorry, something went wrong.
voetberg
No branches or pull requests
Description
The archive metadata plugin sends empty collocation hints to FTS.
The following have been observed in ATLAS and CMS FTS databases for multiple transfers:
I think it could be a side effect that when no policy is configured, the default is to send an empty dict?
If there are no collocation hints, the archive metadata should not be sent.
Steps to reproduce
Observed in production env
Rucio Version
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: