Limiting job array concurrency

[Yuri D'Elia]

Is there a way for an user to specify an upper bound for the number of
jobs running simultaneously on an array?

A practical example for this scenario is to limit concurrent connections
to a shared resource that is external to the cluster. As such, I don't
want really to specify a "Gres" resource, as this would also bind jobs
to the node/s where the resource was assigned and would be not much
better than -w.

Thanks.

[Marcin Stolarek]

Post by Yuri D'Elia
Is there a way for an user to specify an upper bound for the number of
jobs running simultaneously on an array?
A practical example for this scenario is to limit concurrent connections
to a shared resource that is external to the cluster. As such, I don't
want really to specify a "Gres" resource, as this would also bind jobs
to the node/s where the resource was assigned and would be not much
better than -w.
Thanks.

Create licences for this resource?

cheers,
marcin

[Yuri D'Elia]

Post by Marcin Stolarek

Post by Yuri D'Elia
A practical example for this scenario is to limit concurrent connections
to a shared resource that is external to the cluster. As such, I don't
want really to specify a "Gres" resource, as this would also bind jobs
to the node/s where the resource was assigned and would be not much
better than -w.
Thanks.

Create licences for this resource?

Ah yes, Licenses, completely forgot about them. It's a good stop-gap,
thanks.

But it's inconvenient to have to define beforehand a license just to
limit a specific job concurrency.