Sqoop V1.4.6 - Sqoop Export Fails With ConnectException

Hello Fellow Sqoopers!
I’m having some trouble with Sqoop export and wanted to document my findings as the usual Google searching and Apache Sqoop docs aren’t helping.
I’m trying to export a Hive table (sequence file) from AWS EMR to AWS RDS(MySQL) and SQOOP is returning the following error. Please note, I am able to successfully sqoop-import from this MySQL Database into Hive!!!
$ sqoop-export \
--connect jdbc:mysql://: \
--username  \
--password  \
--table  \
--export-dir 'hdfs://172.31.47.117/user/hive/warehouse/HiveTable'
ERROR tool.ExportTool: Encountered IOException running export job: java.net.ConnectException:
Call From
   ip-172-31-47-117.us-west-2.compute.internal/172.31.47.117
to
   ip-172-31-47-117.us-west-2.compute.internal:8020
failed on connection exception: java.net.ConnectException: Connection refused;
For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused
-- Some environmental info from the Master Node (ie. internal IP):
$ hostname -I
172.31.47.117
$ telnet 172.31.47.117 8020
Trying 172.31.47.117...
telnet: connect to address 172.31.47.117: Connection refused.
So of course I can see the cause of the problem. But why on earth is SQOOP-EXPORT trying to connect to itself on port 8020 and what can I do about it?
There is no port-configuration information to gleaned from $SQOOP_HOME/conf/sqoop-site.xml
Kind Regards
Timothy Garza
Database and BI Developer
Collinson Technology Services
Skype: timothy.garza.cts
collinsongroup.com
[Collinson Group]
The Collinson Group Limited; Registered number: 2577557, Registered in England & Wales; Registered Office: Cutlers Exchange, 123 Houndsditch, London, EC3A 7BU.
This e-mail may contain privileged and confidential information and/or copyright material and is intended for the use of the addressee only. If you receive this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete this e-mail from your computer system. You may not deliver, copy or disclose its contents to anyone else. Any unauthorised use may be unlawful. Any views expressed in this e-mail are those of the individual sender and may not necessarily reflect the views of The Collinson Group Ltd and/or its subsidiaries or any other associated company (collectively “Collinson Group”).
As communications via the Internet are not secure Collinson Group cannot accept any liability if this e-mail is accessed by third parties during the course of transmission or is modified or amended in any way following despatch. Collinson Group cannot guarantee that any attachment to this email does not contain a virus, therefore it is strongly recommended that you carry out your own virus check before opening any attachment, as we cannot accept liability for any damage sustained as a result of software virus infection. Senders of messages shall be taken to consent to the monitoring and recording of e-mails addressed to members of the Company.

You should know that Hive version of sequence files is not supported in Sqoop 1 - sequence file is just a container that can be used in many different forms and we’re simply not supporting the way Hive uses them.
Now for the problem:
You have specified in the —export-dir that Sqoop should connect to HDFS instance running on 172.31.47.117 and that is why Sqoop is connecting there (8020 is default port for namenode). If your namenode runs somewhere else, then you have to update your Sqoop command.
Alternatively, if the import works just fine, I would drop the entire part with specifying namenode and use only the directory, e.g. “—export-dir /user/hive/wahourese/HiveTable”.
Jarcec

I am trying to run distcp between 2 hdfs clusters and I am getting a Conne= ctException . The Command I am trying to run is of the form (considering clusters hadoop-= A & hadoop-B): ./hadoop distcp -update hdfs://hadoop-A:8020/dira/part-r-00000 hdfs://hadoo= p-B:8020/dirb/ and I am running it on the destination cluster (hadoop-B). The stacktrace for the exception is : Copy failed: java.net.ConnectException
Hi all, When my cometd server dies, or restarts, in the connected java clients, a ConnectException propagates up and dumps out as follows: 2010-11-22 13:50:42.424:INFO:org.cometd.client.BayeuxClient@575708156: java.net.ConnectException: Connection refused ��������at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ��������at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java
Perhaps someone knows what is causing this problem? I'm new to database connectivity in java so i'm not good at figuring this out yet :) I read over the readme provided with mm mysql and found a very similar error to mine, however i'm running this as a stand alone, not an applet, and the error resembles one generated by an applet's security manager. The exact error produced is: Cannot
Hi, In my test plan I am using one thread group, under which there are 50 threads. I am using tomcat 3.2.2 as the servlet container for my application. When I start my testcase. I get java.net.ConnectException: connection refused. The ramp up period is 0. any suggetions????? thanx in advance Ankit C
Hi, I try to catch a ConnectionException when calling a webservice but I fail to catch it. This is my code: � def testws = Action { implicit request => � � try { � � � Async { � � � � WS.url("http://url-that-does-not-exist.com/").get().map { response => � � � � � Ok("got result from ws") � � � � } � � � } � � } catch { � � � case _ �=> Ok("error") � � } � } I do not see "error" on the page as expected
Hello guys! I'm having a little trouble with JMeter. I have a test that make some HTTP GET on an url that serve an xml document (generated from a database). But when running this test, I received this exception. And as it speak about JMeter on the stack trace, I'm quite sure that the problem doesn't come from my web app :) Here is the ST: java.net.ConnectException: Connection refused: connect
All, We're getting sporadic java.net.ConnectException on random embedded resource samples. The error doesn't always happen suggesting that the file we're requesting does exist on the server, and it when it does occur is isn't necessarily the same embedded resource from occurrence to occurrence. The message seems to be "Connection timed out: connect." I have included the exception stack trace
I've created a couple of dev clusters in ec2 that have worked fine without any special networking configuration.  One of our ops guys wrote some chef scripts to automate staging/production cluster creation and as far as I can see the hadoop configuration is fine - nothing to do with network configuration.  However, when I try to do some black-box testing on the cluster, it fails in the reducer
I am trying to backup (with distcp) my Hadoop cluster so that I can upgrade it without losing all of my data.  I am trying to go from nn01-qa.ny3/ to medium01.ny3/backup Right now, it doesn't work.  How can I fix this problem? Both clusters are CDH3u5 on CentOS 6.3 x64 on the same VMware ESXi 5.1 host.  The network is completely open to each host and all firewalls are turned off.  The only strange
Hi, I'm planning to design an application which can receive files from multiple transports like JMS, FTP, FILE, REST etc. I'm having trouble to handle the ConnectException thrown at route startup if any endpoint(JMS,FTP etc.) is down. I have designed a global exception handler using onException which is able to handle the exceptions once the route is started. Consider following scenarios