hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Schneider <Sch...@TransPac.com>
Subject Re: AWS Hadoop 20.2 AMIs
Date Thu, 09 Dec 2010 20:44:56 GMT
Hi Mike,

At 10:41 AM -0800 11/17/10, Gangl, Michael E (388K) wrote:
>I've been running into an issue today.
>I'm trying to procure 5 c1.xlarge instances on Amazon EC2. I was able to use the 453820947548/bixolabs-hadoop-0.20.2-i386
AMI for my previous m1.large instances, so I figured I could use the c1.xlarge instances with
the x86_64 versions.

Note that the 453820947548/bixolabs-hadoop-0.20.2-i386 AMI (ami-48b54021) was designed for
m1.small and c1.medium instances. We put together a different public AMI (ami-827c8beb) for
m1.large instances.

>When I start these with the src/contrib/ec2/bin scripts, however, the master starts but
then I'm unable to connect to the xlarge instances. I can still use the 1.large instances,
but these are too slow for me, so I'd like to use the bigger machine. Has anyone else been
having problems today, or in the past with getting an AMI to work on the xlarge instances?

At 11:26 AM -0800 11/17/10, Gangl, Michael E (388K) wrote:
>FYI, I commented out the Kernal version in the hadoop-ec2-env.sh script for the c1.xlarge
if statements (at the bottom).
>Before it was using aki-427d952b
>Now it's using aki-b51cf9dc
>And I'm able to connect. Turns out the problem was a hang during the boot. This should
probably be changed in the future releases of the ec2 scripts (if it's not changed already
:) )

The Hadoop 0.20.2's /src/contrib/ec2/bin/hadoop-ec2-env.sh.template actually specifies $AMI_KERNEL=aki-800e5f2
for c1.xlarge:


I haven't tried launching any c1.xlarge instances myself, though.


- Chris
Chris Schneider
TransPac Software, Inc.

View raw message