mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
d7a5274164
If an allocrunner is persisted to the client state but the client stops before task runner can start, we end up with an allocation in the database with allocrunner state but no taskrunner state. This ends up mimicking an old pre-0.9.5 state where this state was not recorded and that hits a backwards compatibility shim. This leaves allocations in the client state that can never be restored, but won't ever be removed either. Update the backwards compatibility shim so that we fail the restore for the allocrunner and remove the allocation from the client state. Taskrunners persist state during graceful shutdown, so it shouldn't be possible to leak tasks that have actually started. This lets us "start over" with the allocation, if the server still wants to place it on the client.
4 lines
119 B
Plaintext
4 lines
119 B
Plaintext
```release-note:bug
|
|
client: remove incomplete allocation entries from client state database during client restarts
|
|
```
|