This is a minor annoyance, but I'm wondering if anyone has found a way
around this.

When whirr creates a hadoop cluster in EC2, I've found that the admin UI
(i.e. the web interface served up at <jobtracker>:50030, e.g.) uses the
public DNS names for all systems until you get down to the individual tasks
on a particular task tracker and want to download some or all of the logs
for a particular log.  At this point, the URLs are rendered using the
private DNS names and are not resolvable outside EC2.

Is there any way to get around this, other than pulling down the cluster
instance manifest and generating /etc/host entries all the private DNS
names pointing to each instance's public IPs?

Reply via email to