Lame Duck Mode

[zakk616]

I am testing restart nats-server during load using ldm with command nats-server --signal ldm and checking the nats-server.service status using systemctl status nats-server.service which says Active: failed instead of Active: incative

NATS Version: 2.10.19
Note: I am using the default lame_duck_duration: 2m and lame_duck_grace_period: 10s

[derekcollison]

If the server does not have alot of client connections it can exit earlier then lame duck duration. If it has no clients it could exit immediately.

[derekcollison]

Would need more info on the server's state before you issue the signal.

[zakk616]

server has only 14 connections, still its not being stopped gracefully and terminating.
neither nats-server --signal ldm works, nor systemctl stop nats-server.service works when ldm is defined in config file.

though when I change the service line:
ExecStop=/bin/kill -s SIGINT $MAINPID
to line:
ExecStop=/bin/kill -V -s SIGINT $MAINPID

Only it works fine, strange!

I am not sure its the OS level issue or at nats-server level.

[ripienaar]

I think if you're setting a ExecStop in the unit file you probably shouldn't make it exit using nats-server --signal but always using the systemctl command.