You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux ip-172-30-0-199 4.4.0-22-generic #40~14.04.1-Ubuntu SMP Fri May 13 17:27:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Issue
We have Amazon autoscale group, and want that every time, when launched new instance some jobs begin work. So we create job with system sheduler. But time to time nomad doesn't launch anything, when newly created amazon instance first launch. As our workaround we use node-drain, every time at instance launch(inti.d script),
Little addon. Seems that nomad launching system jobs, but make it time to time very long. I mean that when instance starts, nomad may frustrate 7-10 minutes before launching anything
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
Nomad v0.4.0
Operating system and Environment details
Linux ip-172-30-0-199 4.4.0-22-generic #40~14.04.1-Ubuntu SMP Fri May 13 17:27:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Issue
We have Amazon autoscale group, and want that every time, when launched new instance some jobs begin work. So we create job with system sheduler. But time to time nomad doesn't launch anything, when newly created amazon instance first launch. As our workaround we use
node-drain
, every time at instance launch(inti.d script),after which nomad begin place system task well. This happens also on nomad 0.3.2
The text was updated successfully, but these errors were encountered: