You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever we need to include a new daemon, we need to explicitly set its count to 0 in tier0-reaper [1] and loadtest [2] configuration which seem to be inheriting the general prod rucio config [3]. Often times, this is overlooked and requires extra attention to fix.
Enhancement Description
Whenever we need to include a new daemon, we need to explicitly set its count to 0 in tier0-reaper [1] and loadtest [2] configuration which seem to be inheriting the general prod rucio config [3]. Often times, this is overlooked and requires extra attention to fix.
[1] https://github.com/dmwm/rucio-flux/blob/main/apps/production/tier0-reaper-rucio-daemons.yaml
[2] https://github.com/dmwm/rucio-flux/blob/main/apps/production/loadtest-rucio-daemons.yaml
[3] https://github.com/dmwm/rucio-flux/blob/main/apps/production/prod-rucio-daemons.yaml
Use Case
Defining new daemons
Possible Solution
I haven't investigated, yet
Related Issues
dmwm/rucio-flux#332
dmwm/rucio-flux#335
The text was updated successfully, but these errors were encountered: