-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
ProhibitOverlap not respected after a restart #14505
Comments
Thanks for reporting this issue @sammynx. Just to clarify, is this what happened?
Is this accurate? Do you have any logs you can provide, and your full jobspec (with any sensitive data removed)? |
This is what happened
This is the entire jobspec:
|
Linking this to #11052. This is possibly a duplicate. |
@sammynx Do you have the logs available, and if so can you tell if a leader election was in progress? |
Hi @DerekStrickland - I was hoping to comment on #11052, but it's been locked. I'd be interested in working on this bug. I'm not sure if @mikenomitch is still involved - but per his comment - I'd be happy to get ramped up and try to resolve this issue. Let me know if I can help! |
@JNProtzman, it turns out that Derek has moved on to greener pastures. But you're definitely welcome to take a look if you're interested! Thanks! |
I believe this issue is now resolved as part of the work done within #16583 which will be released and backported in the near future. I will therefore close this issue. If the bug continues to exist, please feel free to reopen this issue, and we will continue to investigate. |
Nomad version
Output from
nomad version
Nomad v1.3.1 (2b054e3)
Operating system and Environment details
Linux 4.19.0-21-cloud-amd64 #1 SMP Debian 4.19.249-2 (2022-06-30) x86_64 GNU/Linux
Issue
I have a scheduled job running with
ProhibitOverlap=true
in its periodic stanza. When the job was running the machine crashed and when it came back Nomad started the running periodic job again. But when the next period was triggered it started a second one while the first was still running.I expected Nomad to wait until the running job was finished.
Reproduction steps
Expected Result
Actual Result
Job file (if appropriate)
Used periodic config
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: