cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CASSANDRA-868) Stop Cassandra using Cassandra Script
Date Wed, 31 Mar 2010 23:42:27 GMT

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

Eric Evans resolved CASSANDRA-868.
----------------------------------

    Resolution: Won't Fix
      Assignee: Eric Evans

As Jonathan has already mentioned, a remote method that terminates the node is the wrong approach.

You could include a stop argument to bin/cassandra but that would just kill `cat <pid file>`,
which hardly seems worth it (it's just as easy to kill `cat <pid file>`).

> Stop Cassandra using Cassandra Script
> -------------------------------------
>
>                 Key: CASSANDRA-868
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-868
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 0.7
>         Environment: Ubuntu 9.10
> Java 6
>            Reporter: steve
>            Assignee: Eric Evans
>
> When I start Cassandra, I cannot stop it. I can only stop it by kill the process using
"kill <pid>".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message