Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hive >> mail # user >> HWI use on AWS/EMR


Copy link to this message
-
RE: HWI use on AWS/EMR
Thanks for the quick reponse Dean.

Confirmed that http://ec2-XX-AAA-BB-CCC.eu-west-1.compute.amazonaws.com gives the same timeout.

Doesn't specifying http://<hostname>:9999<http://%3chostname%3e:9999> override the requirement for port 80 being open?

Is ssh tunnelling the same as the process described by Ariel in the next reply?

From: Dean Wampler [mailto:[EMAIL PROTECTED]]
Sent: 18 January 2013 16:09
To: [EMAIL PROTECTED]
Subject: Re: HWI use on AWS/EMR

Oops, I overlooked that you have the public domain name in your message. Can you surf to  http://ec2-54-247-61-206.eu-west-1.compute.amazonaws.com ?  If not, does HWI use port 80? Is whatever port it uses blocked by EC2?

If it's blocked you can use ssh to tunnel the port through.

dean
On Fri, Jan 18, 2013 at 10:06 AM, Dean Wampler <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
That's the internal hostname, not visible outside. Use the name like ec2-NNN-NN-NN-NNN.compute-1.amazonaws.com<http://ec2-NNN-NN-NN-NNN.compute-1.amazonaws.com>. It's shown in the EMR console and the elastic-mapreduce script you might have used to launch the cluster.

If that doesn't work, verify that port 80 is not blocked by default. That's certainly true for ports 9XXX used by the JobTracker, etc.

dean

On Fri, Jan 18, 2013 at 9:54 AM, Tony Burton <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
Hi,

I'm trying to get HWI running and accessible from an Amazon Web Services EMR instance. I've hit a blocker early on though, and the documentation is less than illuminating. Can you share any experiences you have had? Specifically, here's what I'm curious about.

- Running on AWS. I've created a Hive job flow on AWS, edited hive-default.xml (in /home/hadoop/.versions/hive-0.8.1/conf) and changed the hive.hwi.war.file to lib/hive-hwi-0.8.1.war.
- HWI starts up fine, but when I try to connect with http://ip-XX-AAA-BBB-CCC.eu-west-1.compute.internal:9999/hwi, I get a timeout message, in Firefox it's "The connection has timed out - The server at ec2-54-247-61-206.eu-west-1.compute.amazonaws.com<http://ec2-54-247-61-206.eu-west-1.compute.amazonaws.com> is taking too long to respond".

Has anyone successfully connected to HWI running on an AWS EMR instance? From the same browser I can connect to HWI on a local Ubuntu box.

Thanks!

Tony
**********************************************************************
Please consider the environment before printing this email or attachments

This email and any attachments are confidential, protected by copyright and may be legally privileged.  If you are not the intended recipient, then the dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system.  Neither Sporting Index nor the sender accepts responsibility for any virus, or any other defect which might affect any computer or IT system into which the email is received and/or opened.  It is the responsibility of the recipient to scan the email and no responsibility is accepted for any loss or damage arising in any way from receipt or use of this email.  Sporting Index Ltd is a company registered in England and Wales with company number 2636842, whose registered office is at Gateway House, Milverton Street, London, SE11 4AP.  Sporting Index Ltd is authorised and regulated by the UK Financial Services Authority (reg. no. 150404) and Gambling Commission (reg. no. 000-027343-R-308898-001).  Any financial promotion contained herein has been issued
and approved by Sporting Index Ltd.

Outbound email has been scanned for viruses and SPAM

--
Dean Wampler, Ph.D.
thinkbiganalytics.com<http://thinkbiganalytics.com>
+1-312-339-1330<tel:%2B1-312-339-1330>
--
Dean Wampler, Ph.D.
thinkbiganalytics.com<http://thinkbiganalytics.com>
+1-312-339-1330

*****************************************************************************
P Please consider the environment before printing this email

www.sportingindex.com<http://www.sportingindex.com>

Inbound email has been scanned for viruses & spam