[CASSANDRA-13436] Stopping Cassandra shows status "failed" due to non-zero exit status

• Type: Sub-task
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Component/s: Packaging
• Assignee: Unassigned
• Reporter: Stefan Podkowinski
• Created: 12/Apr/17 14:36
• Updated: 16/Apr/19 09:30

Description

Systemd will monitor the process from the pid file and save the return status once if has been stopped. In case the process terminates with a status other than zero, it will assume the process terminated abnormaly. Stopping Cassandra using the cassandra script will send a kill signal to the JVM causing it to terminate. If this happen, the JVM will exit with status 143, no matter if shutdown hooks have been executed or not. In order to make systemd recognize this as a normal exit code, the following should be added to the yet to be created unit file:

[Service]
...
SuccessExitStatus=0 143
...

Issue Links

• is related to: CASSANDRA-13148 Systemd support for RPM