Updated by ttereshc almost 5 years ago
No signs of `pulp.server.maintenance.monthly` in the logs for the last 30 days. If task is triggered manually, it works properly and orphaned applicability profiles got cleaned up. Having a lot of orphaned applicability profiles triggers a lot of no-op applicability tasks, it can slow down the whole system if there are too many of those tasks. E.g. A repo with many bound consumers (30K unique profiles) will trigger 3K tasks. It would be useful to make the period for this task configurable.