cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9791) Adjust stop-server.ps1 to behave similarly to stop behavior in cassandra init script
Date Mon, 13 Jul 2015 20:30:05 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Philip Thompson updated CASSANDRA-9791:
---------------------------------------
    Fix Version/s: 2.2.x

> Adjust stop-server.ps1 to behave similarly to stop behavior in cassandra init script
> ------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9791
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9791
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Config
>         Environment: cassandra-2.2 branch.
>            Reporter: Andy Tolbert
>            Priority: Minor
>             Fix For: 2.2.x
>
>         Attachments: CASSANDRA-9791.patch
>
>
> I have a test that repeatedly rolls nodes in a C* cluster.   Occasionally I run into
a case where a node is not restarted because stop-server.ps1 returns before the C* process
had terminated.
> This is because stop-server.ps1 currently will wait for up to 2 seconds for cassandra
to exit from a CTRL+C and then returns.   In practice it can take cassandra longer than that
to exit and the script doesn't give you any indication that cassandra is still running.
> Proposing that stop-server.ps1 behaves the same way as the 'cassandra' init script provided
by dsc21 does:
> {code}start-stop-daemon -K -p "$PIDFILE" -R TERM/30/KILL/5 >/dev/null{code}
> The init script currently sends a SIGTERM (CTRL+C) to the process and if it hasn't terminated
after 30 seconds sends a SIGKILL to it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message