-
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
[documentation] Periodic Dispatch jobs execute immediately #2470
Comments
@nugend I am not seeing that behavior:
|
Can you provide the full example.nomad file? I'll try and reproduce with the example and if the behavior is different I will see if I can figure out what's going on. |
@dadgar I'm seeing similar output from the command line, but I'm using hashi-ui to actually look at most of my jobs, so I noticed that it had attempted to execute. When I look at the HTTP allocations end point, I see that the job is executing. The following jq filter provides a concise summary:
Maybe this is also a bug with the status sub-command? |
Sure:
I am going to close this till it is verified broken because twice I have run it now and it is working correctly. |
@dadgar I can only run the raw_exec driver in my environment. The following task reproduces the issue:
Part of the problem is that you can't see the allocation with just
So, I used the HTTP API to look up the allocations for the dispatch job, took the returned ID (which should be the first one), and can see that it is currently executing by inspecting the logs. If I'm doing something blatantly wrong here with the task definition, please let me know. |
Yeah I see now. It is when dispatched an alloc is made! Will get a fix for 0.5.6 |
This PR fixes an issue in which when a periodic and parameterized job was dispatched, an allocation would be immediately created. Fixes #2470
Awesome! Thanks! |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
0.5.5
Issue
When
nomad job dispatch
ing a periodic dispatch job, the job will begin executing immediately. This is fine, but the behavior is not clearly documented as far as I can tell. Plain batch periodic jobs do not immediately execute and are deferred until the next time as indicated by the periodic stanza.If this is not the intended behavior, then I guess this is a bug?
The text was updated successfully, but these errors were encountered: