Home Forums Sqoop sqoop & Netezza

This topic contains 2 replies, has 2 voices, and was last updated by  Mahesh Balakrishnan 9 months, 2 weeks ago.

  • Creator
    Topic
  • #48280

    Orlando
    Participant

    Trying to get sqoop to dump a table from a netezza rack. All appears to run smoothly, e.g. password is accepted, table is found and it starts to import but after a few minutes the following occurs (I did cut it down a bit) – has anyone this before? Thank you all.

    2014-02-03 14:42:49,926 INFO ipc.Server (Server.java:saslProcess(1347)) – Auth successful for appattempt_1391109297313_0040_000001 (auth:SIMPLE)
    2014-02-03 14:42:49,933 INFO containermanager.ContainerManagerImpl (ContainerManagerImpl.java:startContainerInternal(556)) – Start request for container_1391109297313_0040_01_000001 by user TJ
    2014-02-03 14:42:49,933 INFO containermanager.ContainerManagerImpl (ContainerManagerImpl.java:startContainerInternal(596)) – Creating a new application reference for app application_1391109297313_0040
    2014-02-03 14:42:49,934 INFO nodemanager.NMAuditLogger (NMAuditLogger.java:logSuccess(89)) – USER=TJ IP=10.10.10.13 OPERATION=Start Container Request TARGET=ContainerManageImpl RESULT=SUCCESS APPID=application_1391109297313_0040 CONTAINERID=container_1391109297313_0040_01_000001
    2014-02-03 14:42:49,934 INFO application.Application (ApplicationImpl.java:handle(451)) – Application application_1391109297313_0040 transitioned from NEW to INITING
    2014-02-03 14:42:49,935 INFO application.Application (ApplicationImpl.java:transition(297)) – Adding container_1391109297313_0040_01_000001 to application application_1391109297313_0040
    2014-02-03 14:42:49,990 INFO application.Application (ApplicationImpl.java:handle(451)) – Application application_1391109297313_0040 transitioned from INITING to RUNNING
    2014-02-03 14:42:49,992 INFO container.Container (ContainerImpl.java:handle(871)) – Container container_1391109297313_0040_01_000001 transitioned from NEW to LOCALIZING
    2014-02-03 14:42:49,992 INFO containermanager.AuxServices (AuxServices.java:handle(175)) – Got event CONTAINER_INIT for appId application_1391109297313_0040
    2014-02-03 14:42:49,992 INFO localizer.LocalizedResource (LocalizedResource.java:handle(196)) – Resource hdfs://nxx3-hdp.blah:8020/user/TJ/.staging/job_1391109297313_0040/job.jar transitioned from INIT to DOWNLOADING
    2014-02-03 14:42:49,993 INFO localizer.LocalizedResource (LocalizedResource.java:handle(196)) – Resource hdfs://nxx3-hdp.blah:8020/user/TJ/.staging/job_1391109297313_0040/libjars/avro-mapred-1.5.3.jar transitioned from INIT to DOWNLOADING
    2014-02-03 14:42:49,993 INFO localizer.LocalizedResource (LocalizedResource.java:handle(196)) – Resource hdfs://nxx3-hdp.blah:8020/user/TJ/.staging/job_1391109297313_0040/libjars/snappy-java-1.0.3.2.jar transitioned from INIT to DOWNLOADING
    2014-02-03 14:42:49,996 INFO localizer.LocalizedResource (LocalizedResource.java:handle(196)) – Resource hdfs://nxx3-hdp.blah:8020/user/TJ/.staging/job_1391109297313_0040/libjars/paranamer-2.3.jar transitioned from INIT to DOWNLOADING

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘sqoop & Netezza’ is closed to new replies.

  • Author
    Replies
  • #49592

    Hi Orlando,

    1. Can you check and see if there is any exceptions on the MapReduce job which sqoop initiated for the data transfer apart from the ones which have updated.
    2. Can all the datanodes reach netezza DB?
    3. What is the sqoop command that you have issued?

    -Mahesh

    Collapse
    #48282

    Orlando
    Participant

    Sorry I should have focused on the error line which is very ambigoius:

    2014-02-03 14:42:50,736 INFO nodemanager.ContainerExecutor (ContainerExecutor.java:logOutput(173)) –
    2014-02-03 14:42:50,736 WARN launcher.ContainerLaunch (ContainerLaunch.java:call(314)) – Container exited with a non-zero exit code 1
    2014-02-03 14:42:50,737 INFO container.Container (ContainerImpl.java:handle(871)) – Container container_1391109297313_0040_01_000001 transitioned from RUNNING to EXITED_WITH_FAILURE

    Collapse
Viewing 2 replies - 1 through 2 (of 2 total)