Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Sqoop >> mail # user >> Sqoop import failed


Copy link to this message
-
Re: Sqoop import failed
Hi Krishnan

I second Venkat's thoughts here. The TT nodes can't make a connection to DB
server due to some firewall blockage.

Gateway node is more like a client  that has access to the cluster. You log
on to this machine from your dev environment, to submit jobs into cluster
as your dev environment doesn't have direct access to cluster.

When the TaskTracker nodes/map tasks makes a db connection, it is more or
less of a direct connection that is made. That connection won't take an
extra hop of TT->GateWay->DBServer.

Sqoop to work as desired the db server should be reachable from all nodes
in the cluster. You need to touch base with your admins and make some
exception to the firewall may be to permit this connection alone.
On Wed, Mar 12, 2014 at 6:55 PM, Krishnan Narayanan <
[EMAIL PROTECTED]> wrote:

Regards
       Bejoy

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB