Content Applicability Regeneration for individual consumers is sent to a single worker
The same tags are used when calculating applicability for a single consumer  as for all consumers bound to a specific repo . As a result when multiple consumers are registered within a short amount of time, the tasks to generate content applicability profiles for these consumers are sent to a single worker and the tasks are executed serially.
#4 Updated by mhrivnak almost 4 years ago
We'll need to be careful to ensure that multiple calculations can run safely in parallel. Maybe since we are already batching the calculation and farming it out for parallel execution, the problem is already solved? Is there anything different about doing this for a single consumer?
#11 Updated by ttereshc over 3 years ago
I think applicability calculation for individual consumers is sent to the single worker only in case the task for multiple consumers is triggered.
If one will use the task for single consumer the resource will be reserved for the particular consumer only so calculation for other consumers can be done by other workers.
#12 Updated by ttereshc over 3 years ago
- Status changed from ASSIGNED to CLOSED - WONTFIX
I suggest to use the API call for a single consumer when there is a need to calculate applicability for just one consumer (this is suitable for Katello use cases). Such tasks for different consumers will be sent to multiple workers. So this issue will be solved by using this API call.
Only when one triggers the applicabilty calculation for consumerS then such tasks will be sent to one worker only.
Please re-open this issue if you disagree and think that resource reservation for consumerS call should be removed.
Please register to edit this issue