Raghav Kumar Gautam created SQOOP-1148:
------------------------------------------

             Summary: NPE while commiting import job
                 Key: SQOOP-1148
                 URL: https://issues.apache.org/jira/browse/SQOOP-1148
             Project: Sqoop
          Issue Type: Bug
    Affects Versions: 2.0.0
            Reporter: Raghav Kumar Gautam
            Assignee: Raghav Kumar Gautam


Import job failed with NPE because it was not able to commit the job. This was 
on hadoop2, here is the relevant part of the job log:

2013-07-19 16:35:56,840 INFO [AsyncDispatcher event handler] 
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: job_1374270875354_0004Job 
Transitioned from RUNNING to COMMITTING
2013-07-19 16:35:56,841 INFO [CommitterEvent Processor #1] 
org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler: Processing the 
event EventType: JOB_COMMIT
2013-07-19 16:35:56,882 ERROR [CommitterEvent Processor #1] 
org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler: Could not 
commit job
java.lang.NullPointerException
        at java.lang.String.<init>(String.java:593)
        at 
org.apache.sqoop.job.mr.ConfigurationUtils.loadConfiguration(ConfigurationUtils.java:252)
        at 
org.apache.sqoop.job.mr.ConfigurationUtils.getConfigConnectorConnection(ConfigurationUtils.java:144)
        at 
org.apache.sqoop.job.mr.SqoopDestroyerExecutor.executeDestroyer(SqoopDestroyerExecutor.java:55)
        at 
org.apache.sqoop.job.mr.SqoopFileOutputFormat$DestroyerFileOutputCommitter.commitJob(SqoopFileOutputFormat.java:88)
        at 
org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler$EventProcessor.handleJobCommit(CommitterEventHandler.java:249)
        at 
org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler$EventProcessor.run(CommitterEventHandler.java:212)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
        at java.lang.Thread.run(Thread.java:680)
2013-07-19 16:35:56,886 INFO [AsyncDispatcher event handler] 
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: job_1374270875354_0004Job 
Transitioned from COMMITTING to FAIL_ABORT
2013-07-19 16:35:56,887 INFO [CommitterEvent Processor #2] 
org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler: Processing the 
event EventType: JOB_ABORT
2013-07-19 16:35:56,888 WARN [CommitterEvent Processor #2] 
org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler: Could not 
abort job
java.lang.NullPointerException
        at java.lang.String.<init>(String.java:593)
        at 
org.apache.sqoop.job.mr.ConfigurationUtils.loadConfiguration(ConfigurationUtils.java:252)
        at 
org.apache.sqoop.job.mr.ConfigurationUtils.getConfigConnectorConnection(ConfigurationUtils.java:144)
        at 
org.apache.sqoop.job.mr.SqoopDestroyerExecutor.executeDestroyer(SqoopDestroyerExecutor.java:55)
        at 
org.apache.sqoop.job.mr.SqoopFileOutputFormat$DestroyerFileOutputCommitter.abortJob(SqoopFileOutputFormat.java:96)
        at 
org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler$EventProcessor.handleJobAbort(CommitterEventHandler.java:273)
        at 
org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler$EventProcessor.run(CommitterEventHandler.java:215)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
        at java.lang.Thread.run(Thread.java:680)
2013-07-19 16:35:56,891 INFO [AsyncDispatcher event handler] 
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: job_1374270875354_0004Job 
Transitioned from FAIL_ABORT to FAILED
2013-07-19 16:35:56,892 INFO [Thread-68] 
org.apache.hadoop.mapreduce.v2.app.MRAppMaster: Job end notification started 
for jobID : job_1374270875354_0004
2013-07-19 16:35:56,894 INFO [Thread-68] org.mortbay.log: Job end notification 
attempts left 0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to