Sqoop on Cloudera 5.2 out of nowhere starts failing

14/11/06 17:25:04 INFO mapreduce.Job: Running job: job_1415319646271_0006

14/11/06 17:25:14 INFO mapred.ClientServiceDelegate: Application state is completed. FinalApplicationStatus=FAILED. Redirecting to job history server

14/11/06 17:25:14 INFO mapreduce.Job: Job job_1415319646271_0006 running in uber mode : false

14/11/06 17:25:14 INFO mapreduce.Job: map 0% reduce NaN%

14/11/06 17:25:14 INFO mapreduce.Job: Job job_1415319646271_0006 failed with state FAILED due to:

14/11/06 17:25:14 INFO mapreduce.ImportJobBase: The MapReduce job has already been retired. Performance

14/11/06 17:25:14 INFO mapreduce.ImportJobBase: counters are unavailable. To get this information,

14/11/06 17:25:14 INFO mapreduce.ImportJobBase: you will need to enable the completed job store on

14/11/06 17:25:14 INFO mapreduce.ImportJobBase: the jobtracker with:

14/11/06 17:25:14 INFO mapreduce.ImportJobBase: mapreduce.jobtracker.persist.jobstatus.active = true

14/11/06 17:25:14 INFO mapreduce.ImportJobBase: mapreduce.jobtracker.persist.jobstatus.hours = 1

14/11/06 17:25:14 INFO mapreduce.ImportJobBase: A jobtracker restart is required for these settings

14/11/06 17:25:14 INFO mapreduce.ImportJobBase: to take effect.

14/11/06 17:25:14 ERROR tool.ImportTool: Error during import: Import job failed!

I have not idea why this is happening. It may be something to do with a copy-paste of the command from notepad. If I retype the last parts of the command in the shell, it doesn’t throw that error.

The lame thing is that Google searches for “mapreduce.ImportJobBase: mapreduce.jobtracker.persist.jobstatus.active = true” get nearly nothing besides source code dumps. Whatever the case, if you get that sort of result after running a sqoop command, just retype the whole mess, especially if you copied and pasted it in to the console window.