mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
dfa07e10ed
Batch job allocations that are drained from a node will be moved to an eligible node. However, when no eligible nodes are available to place the draining allocations, the tasks will end up being complete and will not be placed when an eligible node becomes available. This occurs because the drained allocations are simultaneously stopped on the draining node while attempting to be placed on an eligible node. The stopping of the allocations on the draining node result in tasks being killed, but importantly this kill does not fail the task. The result is tasks reporting as complete due to their state being dead and not being failed. As such, when an eligible node becomes available, all tasks will show as complete and no allocations will need to be placed. To prevent the behavior described above a check is performed when the alloc runner kills its tasks. If the allocation's job type is batch, and the allocation has a desired transition of migrate, the task will be failed when it is killed. This ensures the task does not report as complete, and when an eligible node becomes available the allocations are placed as expected.
4 lines
140 B
Plaintext
4 lines
140 B
Plaintext
```release-note:bug
|
|
client: Fixed bug where drained batch jobs would not be rescheduled if no eligible nodes were immediately available
|
|
```
|