[
https://issues.apache.org/jira/browse/CASSANDRA-13492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Podkowinski updated CASSANDRA-13492:
-------------------------------------------
Resolution: Cannot Reproduce
Assignee: Stefan Podkowinski
Fix Version/s: (was: 3.11.0)
Status: Resolved (was: Patch Available)
I haven't been able to reproduce this on CentOS with a build including the PID
directive added in CASSANDRA-13434. Systemd would always recognize the service
as running and would not start the the Cassandra process in that case. Please
re-open issue if the issue still remains and is reproducible post 13434.
> RPM Init: don't attempt to start if it's running
> ------------------------------------------------
>
> Key: CASSANDRA-13492
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13492
> Project: Cassandra
> Issue Type: Sub-task
> Components: Packaging
> Reporter: martin a langhoff
> Assignee: Stefan Podkowinski
> Attachments: 0002-RPM-Init-avoid-starting-cassandra-if-it-is-up.patch
>
>
> We don't check whether Cassandra is running. Attempts to start Cassandra when
> it's already running overwrite the pidfile, make a confusing mess of
> logfiles, _fail to start, as the port is taken_; and then the init script
> cannot bring the first Cassandra process down because the init file has been
> clobbered.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
