Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Sqoop import fail : TCP/IP Connection refused

avatar
Explorer

Sqoop list-tables , sqoop eval is successful


But fails in Sqoop import.

 

sqoop import --connect "jdbc:sqlserver://10.xxx.xxx.xxx:1433; database=Runtime" --username ** --password ****** --table live -m 1

 

The error is :

Error: java.lang.RuntimeException: java.lang.RuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 10.xxx.xxx.xxx, port 1433 has failed. Error: "Connection refused. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".

1 ACCEPTED SOLUTION

avatar
Explorer

Sqoop eval and Sqoop list tables requires only the Name node connection with the SQL server.

But for SQOOP import, all the nodes in the cluster needs to have access to the remote SQL server.

Here the Telnet failed from datanodes. It was due the network settings and firewalls configuration.

Later when every node was able to access the Remote SQL server the SQOOP IMPORT was successful.

View solution in original post

3 REPLIES 3

avatar
Super Guru
Have you tried to verify that you can telnet to sqlserver host from current host on port 1433?

The error message pretty much indicated that your client host is not able to communicate with server host, it could be a network issue, or some firewall settings.

avatar
Explorer

I am able to Telnet to the SQL Server. Connected success

Sqoop eval, Sqoop list-database, Sqoop list-tables are all working.

Able to view the status and Log in the Job Browser.

 

Only sqoop import throws this TCP/IP Connection refused error.

avatar
Explorer

Sqoop eval and Sqoop list tables requires only the Name node connection with the SQL server.

But for SQOOP import, all the nodes in the cluster needs to have access to the remote SQL server.

Here the Telnet failed from datanodes. It was due the network settings and firewalls configuration.

Later when every node was able to access the Remote SQL server the SQOOP IMPORT was successful.