On Wed, Apr 21, 2010 at 10:08 PM, Oleg Anastasjev wrote:
> Hello,
>
> I am testing how cassandra behaves on single node disk failures to know
> what to
> expect when things go bad.
> I had a cluster of 4 cassandra nodes, stress loaded it with client and made
> 2
> tests:
> 1. emulated disk failure
>
> Ideally I think we'd like to leave the node up to serve reads, if a
> disk is erroring out on writes but still read-able. In my experience
> this is very common when a disk first begins to fail, as well as in
> the "disk is full" case where there is nothing actually wrong with the
> disk per
We have a ticket open for this:
https://issues.apache.org/jira/browse/CASSANDRA-809
Ideally I think we'd like to leave the node up to serve reads, if a
disk is erroring out on writes but still read-able. In my experience
this is very common when a disk first begins to fail, as well as in
the "dis
Hello,
I am testing how cassandra behaves on single node disk failures to know what to
expect when things go bad.
I had a cluster of 4 cassandra nodes, stress loaded it with client and made 2
tests:
1. emulated disk failure of /data volume on read only stress test
2. emulated disk failure of /comm
