Hi Jörg,
I'm the author of those slides, and that statement, even when taken out of
context starts with Prefer,
I don't think I need to explain what prefer means, but just in case ...
Using JBOD will be your safest bet as opposed to using something like RAID
/ SAN/ NAS unless you really know
storage? (and then recreate the shards that went
down)
On Saturday, December 13, 2014 3:48:55 PM UTC, Jörg Prante wrote:
The statement is related to performance and I can't agree with it. You can
easily build a RAID 0 system which has massive I/O throughput performance
and is superior
:
The statement is related to performance and I can't agree with it. You
can easily build a RAID 0 system which has massive I/O throughput
performance and is superior to JBOD, because RAID striping does not slow
things down, it is as always as much as fast than a single drive and in
most RAID
just with lower total available storage? (and then recreate the shards that
went down)
On Saturday, December 13, 2014 3:48:55 PM UTC, Jörg Prante wrote:
The statement is related to performance and I can't agree with it. You
can easily build a RAID 0 system which has massive I/O throughput
The statement is related to performance and I can't agree with it. You can
easily build a RAID 0 system which has massive I/O throughput performance
and is superior to JBOD, because RAID striping does not slow things down,
it is as always as much as fast than a single drive and in most RAID levels
When running Elasticsearch on physical hardware you have it create replicas
to make sure no node is a single point of failure. From everyone's
experiance should I use Hardware Raid as well, or is it not needed?
--
You received this message because you are subscribed to the Google Groups
Striping raid is viable for 2 or 3 disks because of the redundancy.
Software raid works fine for me. Hardware raid enables battery backed write
behind but I don't know how important that is with ssds. Either way, we go
2xSSDs per server with os in mirrored raid and data striped.
Depending on your
, 2014 1:30:32 PM UTC, Nikolas Everett wrote:
Striping raid is viable for 2 or 3 disks because of the redundancy.
Software raid works fine for me. Hardware raid enables battery backed write
behind but I don't know how important that is with ssds. Either way, we go
2xSSDs per server with os
If you can architect around the loss of a node and subsequent recovery,
then I reckon it's worth testing the notion of not running RAID.
On 12 December 2014 at 14:30, Nikolas Everett nik9...@gmail.com wrote:
Striping raid is viable for 2 or 3 disks because of the redundancy.
Software raid
Everett wrote:
Striping raid is viable for 2 or 3 disks because of the redundancy.
Software raid works fine for me. Hardware raid enables battery backed write
behind but I don't know how important that is with ssds. Either way, we go
2xSSDs per server with os in mirrored raid and data striped
I cannot put my finger on it, but I think I recall that someone in this
group once said that ES is IO intensive, that RAID would slow things down,
arguing in favor of redundant servers over RAID. Does that still make sense?
On Fri, Dec 12, 2014 at 8:00 AM, Mark Walkom markwal...@gmail.com wrote
Just went through these slides
https://speakerdeck.com/bhaskarvk/scaling-elasticsearch-washington-dc-meetup
First of all, thats one HUGE cluster
Second, Prefer JBODs for data disks over RAID, SAN/NAS, would be ok,
maybe then to be safe go with 2x replicas, goes well with having 3x nodes
12 matches
Mail list logo
