On Mon, Nov 30, 2015 at 11:29 AM, S C wrote:
> It is inevitable that the repairs are needed to keep consistency
> guarantees. Is it worthwhile to consider RAID-0 as we get more storage? One
> can treat loss of disk as loss of node and rebuild the node and repair. Any
> other suggestions are most
From: Robert Coli
Sent: Friday, April 10, 2015 6:51 PM
To: user@cassandra.apache.org
Subject: Re: Moving SSTables from one disk to another
On Fri, Apr 10, 2015 at 4:30 PM, Jonathan Haddad
mailto:j...@jonhaddad.com>> wrote:
However, it was pointed out to me that
https://issues.apache.or
On Fri, Apr 10, 2015 at 4:30 PM, Jonathan Haddad wrote:
> However, it was pointed out to me that
> https://issues.apache.org/jira/browse/CASSANDRA-6696 will be a better
> solution in a lot of cases.
Thank you for the interesting link about a theoretical usage which would
make JBOD worth using.
I had submitted this issue which could have had (in theory) some
serious performance benefit when using JBOD:
https://issues.apache.org/jira/browse/CASSANDRA-8868
However, it was pointed out to me that
https://issues.apache.org/jira/browse/CASSANDRA-6696 will be a better
solution in a lot of cases
On Fri, Apr 10, 2015 at 4:00 PM, Roman Tkachenko
wrote:
> * Can I just move some SSTables data files from "sstables2" to "sstables1"
> which has much more free disk space? Will Cassandra start fine after that
> and not lose any data?
>
Cassandra generally discovers files in its data directories
Hey guys,
We're running Cassandra with two data directories, let's say
/data/sstables1 and /data/sstables2, which are in fact two separate (but
identical) disks. The problem is that the disk where "sstables2" is mounted
is running out of space and large SSTables stored there cannot be compacted.
