Skip to content

Job Array with queueSize exceeds queueSize #5920

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Joon-Klaps opened this issue Mar 25, 2025 · 1 comment · May be fixed by #6047
Open

Job Array with queueSize exceeds queueSize #5920

Joon-Klaps opened this issue Mar 25, 2025 · 1 comment · May be fixed by #6047
Assignees
Labels

Comments

@Joon-Klaps
Copy link
Contributor

Joon-Klaps commented Mar 25, 2025

When combining both executor.queueSize and process.array , I’m reguraly surpassing the executor.queueSize limit is this because the array jobs are seen as a single job?

For example:

process.array = 30
executor.queueSize = 40

The total amount of concurrent jobs running can exceed 60.

Would it be possible to have more control over this?

@bentsherman
Copy link
Member

Good catch. I thought we handled this case when we released it but maybe it got lost in some refactoring.

The task polling monitor needs to consider the job array size when deciding whether it can submit a task:

protected boolean canSubmit(TaskHandler handler) {
(capacity>0 ? runningQueue.size() < capacity : true) && handler.canForkProcess() && handler.isReady()
}

@jorgee can you write a fix for this when you have time

@jorgee jorgee linked a pull request May 7, 2025 that will close this issue
@jorgee jorgee linked a pull request May 7, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants