Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Job timeout doesn't work if threadpool is full #410

Closed
To-om opened this issue May 24, 2022 · 0 comments
Closed

Job timeout doesn't work if threadpool is full #410

To-om opened this issue May 24, 2022 · 0 comments
Assignees
@To-om
Labels
bug
Milestone
3.1.5

Comments

@To-om
Copy link
Contributor

To-om commented May 24, 2022

Request Type

Bug

Problem Description

When threadpool is full, there is no thread available to kill the stuck jobs.
The job "controller" should be run in a different threadpool.
@To-om To-om added the bug label May 24, 2022
@To-om To-om added this to the 3.1.5 milestone May 24, 2022
@To-om To-om self-assigned this May 24, 2022
To-om added a commit that referenced this issue Jun 21, 2022
@To-om
#410 Check the job timeout from the main threadpool
7d02023
To-om added a commit that referenced this issue Jun 21, 2022
@To-om
#410 Handle job in one thread
b6925bd
@To-om To-om closed this as completed Jun 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@To-om To-om

Labels
bug
Projects
None yet
Milestone
3.1.5
Development

No branches or pull requests
1 participant
@To-om