incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Hendry" <dan.hendry.j...@gmail.com>
Subject RE: shutdown by KILL
Date Wed, 09 Nov 2011 00:31:39 GMT
I *thought* Cassandra was supposed to have a crash only design[1]. My understanding is that
it is safe to simply kill the process and with the regular TERM signal and, shutdown would
be blocked on fsyncing the commit log but nothing else (obviously not true if you kill -9
the sucker) even when using periodic commit log mode. Again, my understanding is that the
disable thrift/gossip commands have no functional purpose (both are going to go down with
as part of drain are they not?). Issuing a 'drain' only minimizes the amount of commit log
which needs to be replayed when starting back up.

[1] Best reference I could find for 'crash only': http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Stopping-Cassandra-gracefully-td3865563.html


Dan

-----Original Message-----
From: Radim Kolar [mailto:hsn@sendmail.cz] 
Sent: November-08-11 6:29
To: user@cassandra.apache.org
Subject: Re: shutdown by KILL

> Ooops, sorry about that. I overlooked the drain. Sorry for the misinformation!
>
cassandra still replays log file even on clean shutdown via nodetool 
drain. It usually takes a while. I don't think it has concept of 
clean-shutdown like SQL databases.
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.920 / Virus Database: 271.1.1/4004 - Release Date: 11/08/11 02:34:00


Mime
View raw message