Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Zookeeper >> mail # user >> EC2 disk configuration for zookeeper? One big disk or two smaller ones per node?


+
Brian Tarbox 2012-10-09, 13:03
+
Ted Dunning 2012-10-09, 15:29
+
Eric Fleischman 2012-10-09, 15:47
Copy link to this message
-
Re: EC2 disk configuration for zookeeper? One big disk or two smaller ones per node?
I have some experience with these.

On Tue, Oct 9, 2012 at 4:47 PM, Eric Fleischman <[EMAIL PROTECTED]>wrote:

> * Using high IOPS instances
>

Haven't tried this.
> * Using multiple disks and doing OS level RAID across them to present a
> single logical disk to the app
>

This typically is very dangerous unless you can somehow arrange for disks
not to present lowest common denominator performance.
> * Local vs. EBS volumes
>

Local tends to be much lower variance.  EBS can show 10:1 variations in
performance.  Even the same volume can change dramatically over time.

 * Standard vs. provisioned IOPS w/EBS
>

Haven't tried this.
+
Andrew Purtell 2012-10-10, 00:06
+
JL 2012-10-10, 03:25
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB