cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2118) Provide failure modes if issues with the underlying filesystem of a node
Date Tue, 14 Aug 2012 22:55:38 GMT


Jonathan Ellis commented on CASSANDRA-2118:

bq. The enum is there for logging purposes only

I'd say let's just log the exception object and give it a decent toString.

bq. What if there is no longer an issue

Having the operator clear out the blacklist files on restart isn't unreasonable if that's
what he wants.
> Provide failure modes if issues with the underlying filesystem of a node
> ------------------------------------------------------------------------
>                 Key: CASSANDRA-2118
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message