Actually I was wrong– our patch will disable gosisp and thrift but leave the process running:
https://issues.apache.org/jira/browse/CASSANDRA-2118 If people are interested in that I can make sure its up to date with our latest version. -ryan On Mon, Jul 25, 2011 at 10:07 AM, Ryan King <r...@twitter.com> wrote: > We have a patch somewhere that will kill the node on IOErrors, since > those tend to be of the class that are unrecoverable. > > -ryan > > On Thu, Jul 7, 2011 at 8:02 PM, Jonathan Ellis <jbel...@gmail.com> wrote: >> Yeah, ideally it should probably die or drop into read-only mode if it >> runs out of space. >> (https://issues.apache.org/jira/browse/CASSANDRA-809) >> >> Unfortunately dealing with disk-full conditions tends to be a low >> priority for many people because it's relatively easy to avoid with >> decent monitoring, but if it's critical for you, we'd welcome the >> assistance. >> >> On Thu, Jul 7, 2011 at 8:34 PM, Donna Li <donna...@utstar.com> wrote: >>> All: >>> >>> When one of the cassandra servers disk full, the cluster can not work >>> normally, even I make space. I must reboot the server that disk full, the >>> cluster can work normally. >>> >>> >>> >>> Best Regards >>> >>> Donna li >> >> >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder of DataStax, the source for professional Cassandra support >> http://www.datastax.com >> >
