[
https://issues.apache.org/jira/browse/CASSANDRA-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028229#comment-13028229
]
Thibaut edited comment on CASSANDRA-2118 at 5/3/11 1:49 PM:
------------------------------------------------------------
Could you add another state ("stop") which would kill cassandra? Also standart
as default is risky, as it can kill an entire cluster (CASSANDRA-2394)
was (Author: tbritz):
Could you add another state ("stop") which would kill cassandra?
> Provide failure modes if issues with the underlying filesystem of a node
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-2118
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2118
> Project: Cassandra
> Issue Type: Sub-task
> Affects Versions: 0.8 beta 1
> Reporter: Chris Goffinet
> Assignee: Chris Goffinet
> Attachments:
> 0001-Provide-failure-modes-if-issues-with-the-underlying-.patch,
> 0001-Provide-failure-modes-if-issues-with-the-underlying-v2.patch,
> 0001-Provide-failure-modes-if-issues-with-the-underlying-v3.patch
>
>
> CASSANDRA-2116 introduces the ability to detect FS errors. Let's provide a
> mode in cassandra.yaml so operators can decide that in the event of failure
> what to do:
> 1) standard - means continue on all errors (default)
> 2) read - means only stop gossip/rpc server if 'reads' fail from drive,
> writes can fail but not kill gossip/rpc server
> 3) readwrite - means stop gossip/rpc server if any read or write errors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
