Lameduck mode does not work in 'no_sandbox' mode.

[NoahHahm]

Observed behavior

hi,

After running node as a lameduck
There is no way to run a new nex node up & (background mode)

[INF] 2024-07-01 15:44:57 - Publishing node lame duck entered event

lameduck mode starts and doesn't end.
the only way is to forcefully terminate the nex process.

Expected behavior

The node should shut down gracefully in no_sandbox mode.

Nex and NATS version

nex --version
v0.2.5 [27f46b4] | Built-on: 2024-06-14T20:34:24Z

Host environment

No response

Steps to reproduce

No response

[jordan-rash]

Hi @NoahHahm. The command behaves this way on purpose in order to allow you to move workloads from one node to another. We have talked about shutting down the node once no workloads were detected, but we haven't implemented that yet. However, to your point, in order to make it match the behavior of nats-server, I expect we will eventually make the behaviors mirror one another. I will leave this issue open as a tracker...let us refine some of the "workload migration" documentation, then we can revisit this feature at that time