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.

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

Job driver: wait for in-flight jobs upon SIGTERM #1555

Merged
merged 1 commit into from
Jul 5, 2023

Conversation

divergentdave
Copy link
Contributor

Fixes #1502.

@divergentdave divergentdave requested a review from a team as a code owner July 3, 2023 17:05
min_job_discovery_delay,
max_job_discovery_delay,
max_concurrent_job_workers,
max_concurrent_job_workers_u32,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, rather than storing the same value twice, do the conversion at point-of-use. It looks like the _u32 version is only used in one place, during shutdown, so this should be OK. We can keep an attempted conversion in new to validate that the given value can be represented as a u32, then unwrap when we do the conversion "for real".

@divergentdave divergentdave force-pushed the david/job-driver-wait-in-flight branch from d635490 to ff070f8 Compare July 5, 2023 15:04
@divergentdave divergentdave merged commit 5df3bc5 into main Jul 5, 2023
6 checks passed
@divergentdave divergentdave deleted the david/job-driver-wait-in-flight branch July 5, 2023 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Graceful shutdown of job drivers
2 participants