forked from proxmox-mirrors/proxmox
![]() if setting up a new worker fails after it has been inserted into the WORKER_TASK_LIST, we need to clean it up instead of bubbling up the error right away, else we "leak" the worker task and it never finishes.. a worker task that never finishes will indefinitely block shutdown of the rest server process, including the "old" process when reloading the rest server. this issue was found in the wild on a system with lock contention on the file-based lock covering task index updating leading to lock acquiring timeouts. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com> |
||
---|---|---|
.. | ||
debian | ||
examples | ||
src | ||
Cargo.toml |