From: mcasandra [mailto:mohitanch...@gmail.com]
Sent: Tuesday, June 28, 2011 7:55 PM
To: cassandra-u...@incubator.apache.org
Subject: Re: RAID or no RAID
aaron morton wrote:
>
>> Not sure what the intended purpose is, but we've mostly used it as an
>> emergency disk-capacity-increa
aaron morton wrote:
>
>> Not sure what the intended purpose is, but we've mostly used it as an
>> emergency disk-capacity-increase option
>
> Thats what I've used it for.
>
> Cheers
>
How does compaction work in terms of utilizing multiple data dirs? Also, is
there a reference on wiki somew
> Not sure what the intended purpose is, but we've mostly used it as an
> emergency disk-capacity-increase option
Thats what I've used it for.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 28 Jun 2011, at 15:55, Dan Kuebrich
Not sure what the intended purpose is, but we've mostly used it as an
emergency disk-capacity-increase option. It's not as good as raid because
each disk size is counted individually (a compacted sstable can only be on
one disk) so compaction size limits aren't expanded as one might expect.
On Mo
I thought there is an option to give multiple data dirs in cassandra.yaml.
What's the purpose of that?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/RAID-or-no-RAID-tp6522904p6523523.html
Sent from the cassandra-u...@incubator.apache.org mailing
If you have a quality HW raid controller with proper performance (and far from
all have good performance) you cam definitely benefit from a battery backed up
write cache on it, although the benefits will not be huge on raid 0.
Unless you get a really good price on that high performance HW raid
RAID0 so you have one big volume.
For performance (cassandra does not stripe sstables across the data dirs) and
otherwise you'll have fragmentation and wont be able to utilise all your space.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpic
