You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/08/15 01:01:38 UTC

[jira] [Comment Edited] (CASSANDRA-2118) Provide failure modes if issues with the underlying filesystem of a node

    [ https://issues.apache.org/jira/browse/CASSANDRA-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434613#comment-13434613 ] 

Jonathan Ellis edited comment on CASSANDRA-2118 at 8/15/12 10:00 AM:
---------------------------------------------------------------------

bq. May be worth adding another option: best_effort_with_repair

Let's save this for a followup after we see how well the blacklisting actually works in production. :)

And since this is the main reason we'd want to persist the blacklist, I'm okay with punting that down the road too.
                
      was (Author: jbellis):
    bq. May be worth adding another option: best_effort_with_repair

Let's save this for a followup after we see how well the blacklisting actually works in production. :)
                  
> 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
>          Components: Core
>            Reporter: Chris Goffinet
>            Assignee: Aleksey Yeschenko
>             Fix For: 1.2
>
>         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, 2118-tweaked.txt, CASSANDRA-2118-part1.patch, CASSANDRA-2118-v1.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira