Skip to content
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

Retire check_unlocked_replicas #140

Open
dchristidis opened this issue Aug 2, 2024 · 2 comments · May be fixed by #148
Open

Retire check_unlocked_replicas #140

dchristidis opened this issue Aug 2, 2024 · 2 comments · May be fixed by #148

Comments

@dchristidis
Copy link
Contributor

ATLAS wishes to retire the check_unlocked_replicas probe.

Its first query counts the number of replicas with a set tombstone across all RSEs. In an instance where having unlocked replicas is the norm, this number conveys no useful information. The per-RSE information is already calculated in check_deletable_replicas and stored as RSE usage counter.

Its second query further limits the first to replicas whose tombstone is more than two hours in the past. Since the tombstone is set to either the time of the creation of the replica or its last use, this query makes no sense.

@ericvaandering, if CMS would like to keep using it, then it will be moved to the cms directory. Otherwise, it will be moved to the attic directory.

@ericvaandering
Copy link
Contributor

We do use this, so let's move it. Can we do this with the Rucio 36 release?

@dchristidis
Copy link
Contributor Author

I’m genuinely curious, how do you extract any piece of useful information out of these two numbers?

@dchristidis dchristidis linked a pull request Aug 7, 2024 that will close this issue
@dchristidis dchristidis linked a pull request Aug 7, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants