Hadoop的EC2上的VS弹性的Map Reduce [英] Hadoop on EC2 vs Elastic Map Reduce

问题描述

我想，以评估这两个选项之间的差异。这里有一些优点和缺点我能想到的：

I'm trying to evaluate the differences between these two options. Here are some pros and cons I can think of :

弹性的Map Reduce从亚马逊=>更好的支持，无需管理集群，更昂贵的（？） EC2 + Hadoop的=>更多的控制你的Hadoop配置，更便宜（？）

Elastic Map Reduce => Better support from Amazon, No need to administer cluster, More Expensive (?) EC2 + Hadoop => More control of your hadoop configuration, Cheaper (?)

我想知道如果任何人有可能基准EC2 + Hadoop的相一相EMR的表现？是否有成本大型群集部署任何显著的区别？存在什么其他方面的差异？

I'm wondering if anyone might have benchmarked the performance of EC2 + Hadoop vis a vis EMR? Is there any significant difference in cost for large cluster deployments? What other differences exist?

推荐答案

好，管理/监控/维护集群本身并不是一个小任务。 使用电子病历真的，你可以得到配置的机器，并和您的自定义启动code。在任何时间运行。 除了做所有这些事情EMR提供了很多其他工具/选项/设施了。

Well, administering/monitoring/maintaining a cluster isn't a small task in itself. Using EMR really you could get machines configured and up and running with your custom bootstrap code in no time. Apart from doing all these things EMR provides a A lot of other tools/options/facilities too.

在这里，您不必担心终止作业完成后的簇，你一定能实现的方式为自己的EC2 + Hadoop的设置，但电子病历在一个整洁的方式做到这一点你。

Here you don't have to worry about terminating a cluster after the jobs are done, you can surely implement a way for yourself in the EC2+Hadoop setup, but EMR does this for you in a neat way.

你也有设施，以调整集群尺寸即使在您的作业运行！

Also you have facility to resize the cluster size even while your jobs are running!

的Pig和Hive中可用的电子病历中也含有的补丁，这使得它更容易使用文件的S3。

The Pig and Hive that are available with EMR also contain patches which make it easier to work with files in S3.

甚至<一href="http://www.quora.com/What-are-the-advantages-of-Amazon-EMR-vs-your-own-EC2-instances-vs-running-Hadoop-locally">here在这个答案，你可能会发现电子病历已被赋予了上风。

Even here in this answer you may find that EMR has been given an upper hand.

这篇关于Hadoop的EC2上的VS弹性的Map Reduce的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！