The intention is to allow the use of multiple disks without RAID or logical volume management. We have found that there are a lot of downsides to RAID--in particular a huge throughput hit. Since we already have a parallelism model due to partitioning and a fault tolerance model with replication RAID doesn't actually buy much. With this feature you can directly mount multiple disks as their own directory and the server will randomly assign partitions to them.
Obviously this will only work well if there are enough high-throughput partitions to make load balance evenly (e.g. if you have only one big partition per server then this isn't going to work).
On Wed, Jun 19, 2013 at 11:01 PM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
Yeah we didn't go as far as adding weighting or anything like that--I think we'd be open to a patch that did that as long as it was optional. In the short term you can obviously add multiple directories on the same disk to increase its share.
On Thu, Jun 20, 2013 at 12:59 PM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
I'm getting ready to try out this configuration (use multiple disks, no RAID, per broker). One concern is the procedure for recovering if there is a disk failure.
If a disk fails, will the broker go offline, or will it continue serving partitions on its remaining good disks? And if so, is there a procedure for moving the partitions that were on the failed disk, but not necessarily all the others on that broker?
Jason On Thu, Jun 20, 2013 at 3:15 PM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext