Kobzol
commented
9 months ago Hi, I'll answer these separately:
1) This option wasn't shown in the alloc queue table, but it will be once this PR is merged.
2) In general, your understanding of the option is correct. If you set max worker count to N, the given allocation queue shall not ever allow more than N workers to run in parallel. However, note that this parameter only applies to a single allocation queue. If you have multiple allocation queues, you can have more than N workers (you can also of course start additional workers manually).
But looking at the number of running jobs, I see I have 24 of them:
The number of running HyperQueue jobs is affected purely by the amount of available resources. If each job has a single task that requires 1 CPU, and you have a single worker with 128 cores, you could have 128 HQ jobs running even if you have only a single worker. So without more context, it's not enough to just look at the amount of HQ jobs.
But I see the 10 in hq alloc info 5 (dropping previous finished workers from the list to make it shorter):
This is what you should see. There should be at most 10 running workers.
I see the same when listing workers:
This either means that you have multiple allocation queues, or have started workers by some other means, or there is a bug in HQ.
svatosFZU
Hi, I am trying to limit the rate at which out allocation is depleted. For that, I thought the max-worker-count option of allocation queue would be the way to do it. Now, watching it run, I have few questions about it. 1.) Is there a way to see that the option was propagated to the HQ? The
hq alloc listdoes not show it:and
hq alloc info 5does not show details of the allocation setting.2.) How does it actually work? According to the docs (https://it4innovations.github.io/hyperqueue/v0.16.0/deployment/allocation/#max-worker-count), it should set maximum number of workers that can be queued or running. So, I set the allocation queu like this:
With one allocation queue running 1 worker per allocation and maximum of 10 workers, I assumed that I would have maximum of 10 running workers/jobs. But looking at the number of running jobs, I see I have 24 of them:
I see the same when listing workers:
But I see the 10 in
hq alloc info 5(dropping previous finished workers from the list to make it shorter):I am rather confused by this situation. So, can max-worker-count be used to limit number of running jobs?