[
https://issues.apache.org/jira/browse/CASSANDRA-13436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068012#comment-16068012
]
Stefan Podkowinski commented on CASSANDRA-13436:
------------------------------------------------
You might want to check the unit file by Tomas, linked in CASSANDRA-13148. The
ticket would also be a good place to continue the discussion on how to
implement systemd support in detail.
> Stopping Cassandra shows status "failed" due to non-zero exit status
> --------------------------------------------------------------------
>
> Key: CASSANDRA-13436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13436
> Project: Cassandra
> Issue Type: Sub-task
> Components: Packaging
> Reporter: Stefan Podkowinski
>
> 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:
> {noformat}
> [Service]
> ...
> SuccessExitStatus=0 143
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
