[WHIRR-492] Hadoop TaskTrackers on EC2 mix of internal and external host names

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.7.0
• Component/s: service/hadoop

Environment

EC2

• Assignee: Unassigned
• Reporter: Tim Robertson
• Created: 30/Jan/12 14:50
• Updated: 03/Feb/12 22:57

Description

Running a 1 master, 3 node cluster of Hadoop + HBase, I see on the Hadoop task trackers
the following hosts:

1) domU-12-31-39-0B-C1-81.compute-1.internal
2) ip-10-66-197-215.ec2.internal
3) domU-12-31-39-0E-F2-41.compute-1.internal

This is consistent with both the trunk (today) and 0.7.0.2, and all
tasks on node 2) above then fail.

My config is the following:
whirr.cluster-name=hbase
whirr.instance-templates=1
zookeeper+hadoop-namenode+hadoop-jobtracker+hbase-master,3
hadoop-datanode+hadoop-tasktracker+hbase-regionserver
whirr.provider=aws-ec2
whirr.identity=${env:AWS_ACCESS_KEY_ID}
whirr.credential=${env:AWS_SECRET_ACCESS_KEY}
whirr.hardware-id=c1.xlarge
whirr.image-id=us-east-1/ami-da0cf8b3
whirr.location-id=us-east-1