Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 6 Feb 2011 06:10:30 +0000 (UTC)
From: "Chris Goffinet (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1985251880.2374.1296972630943.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (CASSANDRA-2118) Provide failure modes if issues
 with the underlying filesystem of a node
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Goffinet updated CASSANDRA-2118:
--------------------------------------

    Issue Type: Sub-task  (was: Improvement)
        Parent: CASSANDRA-2116

> 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
>            Reporter: Chris Goffinet
>            Assignee: Chris Goffinet
>
> 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) Value '0' means continue on all errors (default)
> 2) Value '1' means only kill the server if 'reads' fail from drive, writes can continue
> 3) Value '2' means kill the server if read or write errors.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira