-Re: Hosting Hadoop
Dhaval Shah 2013-10-16, 18:57
Thanks for sharing the experience Alex. I kind of anticipated the kind of issues you mentioned here but just wanted to make sure I explore all possible options
On Wednesday, 16 October 2013 1:34 PM, alex bohr <[EMAIL PROTECTED]> wrote:
Sorry just saw this email (oops) so might not be relevant - but:
We didn't encounter too much Funky issues that we were worried about regarding random resource constraints or random outages that might happen when sharing a physical box with unknown neighbors.
But overall we feel the virtualization is robbing us of significant CPU, and more importantly they don't have ideal instance types. The M1.xlarges are too small storage wise (we ended up paying for more CPU than we needed to get the amount of storage we needed) and the hs1.8xlarge are too big - they have 24 drives and it feels like we lose a good amount of CPU controlling IO across all those drives, and we now have significantly more storage than we need in order to get enough CPU to keep our SLAs.
For initial set-up - AWS is way quicker than owning hardware. But if you already have hardware, moving to AWS I think will increase your monthly bills to get comparable performance.
On Wed, Aug 21, 2013 at 11:36 AM, Dhaval Shah <[EMAIL PROTECTED]> wrote:
Alex, did you run into funky issues with EC2/EMR? The kind of issues that would come up because its a virtualized environment? We currently own our hardware and are just trying to do an ROI analysis on whether moving to Amazon can reduce our admin costs. Currently administering a Hadoop cluster is a bit expensive (in terms of man hours spent trying to replace disks and so on) and we are exploring whether its possible to avoid some of those costs
> From: alex bohr <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Cc: Dhaval Shah <[EMAIL PROTECTED]>
>Sent: Monday, 12 August 2013 1:41 PM
>Subject: Re: Hosting Hadoop
>I've had good experience running a large hadoop cluster on EC2 instances. After almost 1 year we haven't had any significant down time, just lost a small # of data nodes.
>I don't think EMR is an ideal solution if your cluster will be running 24/7.
>But for running a large cluster, I don't see how you it's more cost efficient to run in the cloud than to own the hardware and we're trying to move off the cloud onto our own hardware. Can I ask why you're looking to move to the cloud?
>On Fri, Aug 9, 2013 at 10:42 AM, Nitin Pawar <[EMAIL PROTECTED]> wrote:
>check altiscale as well
>>On Fri, Aug 9, 2013 at 3:05 AM, Dhaval Shah <[EMAIL PROTECTED]> wrote:
>>Thanks for the list Marcos. I will go through the slides/links. I think that's helpful
>>> From: Marcos Luis Ortiz Valmaseda <[EMAIL PROTECTED]>
>>>To: Dhaval Shah <[EMAIL PROTECTED]>
>>>Cc: [EMAIL PROTECTED]
>>>Sent: Thursday, 8 August 2013 4:50 PM
>>>Subject: Re: Hosting Hadoop
>>>Well, all depends, because many companies use Cloud Computing
>>>platforms like Amazon EMR. Vmware, Rackscpace Cloud for Hadoop
>>>There a lot of companies using HBase hosted in Cloud. The last
>>>HBaseCon was full of great use-cases:
>>>HBase at Groupon
>>>A great talk by Benoit for Networking design for HBase:
>>>Using Coprocessors to Index Columns in an Elasticsearch Cluster