Create overview page for the suspicious replica recoverer daemon #373
Conversation
|
The text is OK. I would add a schema describing the state machine similar to https://github.com/rucio/documentation/blob/main/website/static/img/request_state_transition_chart.svg even if it might be a bit complicated to fit everything in just one figure |
| -**ignore**: this is the default policy. Datatypes and scopes can be explicitly set to be ignored, which highlights that a decision has purposefully been made to not perform any actions on these replicas. This is done to prevent mistakes in the future. | ||
| -**declare bad**: this dictates that any associated datatypes or scopes will be declared `BAD` by the daemon. | ||
| -**dry run**: this policy makes the daemon handle the replicas as if they were to be declared `BAD`, but at the final step, no actions are taken. This results in log messages with which it becomes possible to see how many replicas of the given datatype/scope would be declared `BAD` by the daemon. | ||
|
|
There was a problem hiding this comment.
You should mention that the poilcy is a json file and show an example
|
Can you add a reference to this page here? Could be useful to also understand why replicas become suspicious in the first place and where the recoverer daemon comes in |
|
Ping @ChristophAmes would you mind still doing these changes? |
|
I spent a while to read this daemon's code and adapt it into CMS. I'd like to add things into its documentation including this flow chart [1] and how it should be configured [2], which isn't trivial. If this PR is going to merged, I can wait and make a new PR to add my changes. [1]https://cmsdmops.docs.cern.ch/CMSRucio/Daemon_configurations/image.png |
ChristophAmes
force-pushed
the
372-Create_overview_page_for_the_suspicious_replica_recoverer_daemon
branch
2 times, most recently
from
326d12c
to
1f1a888
Compare
|
Sorry I haven't responded, I've been rather busy. |
| -**declare bad**: this dictates that any associated datatypes or scopes will be declared `BAD` by the daemon. | ||
| -**dry run**: this policy makes the daemon handle the replicas as if they were to be declared `BAD`, but at the final step, no actions are taken. This results in log messages with which it becomes possible to see how many replicas of the given datatype/scope would be declared `BAD` by the daemon. | ||
|
|
||
| The replica polices can easily be expanded in the future. |
There was a problem hiding this comment.
| The replica polices can easily be expanded in the future. | |
| The replica policies can easily be expanded in the future. |
ChristophAmes
force-pushed
the
372-Create_overview_page_for_the_suspicious_replica_recoverer_daemon
branch
from
1f1a888
to
fa7ed96
Compare
The suspicious replica recoverer daemon isn't easy to understand at first glance. Therefore, an overview page for the suspicious replica recoverer daemon will be created, which will explain the general structure of the daemon and what the goals of each step are.