[ 
https://issues.apache.org/jira/browse/HADOOP-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711564#action_12711564
 ] 

Ramya R commented on HADOOP-5850:
---------------------------------

The patch seems to introduce a new error. The taskdetails.jsp page of job setup 
and cleanup tasks throws a NullPointerException. This is the case with all the 
jobs' setup and cleanup tasks. Below is the Exception seen on the UI:
java.lang.NullPointerException
at 
org.apache.hadoop.mapred.TaskInProgress.getSplitNodes(TaskInProgress.java:1034)
at 
org.apache.hadoop.mapred.taskdetails_jsp._jspService(taskdetails_jsp.java:288)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:4

> map/reduce doesn't run jobs with 0 maps
> ---------------------------------------
>
>                 Key: HADOOP-5850
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5850
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.20.0
>            Reporter: Owen O'Malley
>            Assignee: Vinod K V
>            Priority: Critical
>             Fix For: 0.20.1
>
>         Attachments: HADOOP-5850-20090519.1.txt, HADOOP-5850-20090519.txt, 
> HADOOP-5850-20090520-svn-branch-20.v2.txt, HADOOP-5850-20090520-svn.1.txt
>
>
> Currently, the framework ignores jobs that have 0 maps. This is incorrect. 
> Many pipelines need the job to run (if nothing else, to create the output 
> directory!) so that subsequent jobs don't fail. Effectively, there will be no 
> map tasks and the reduce tasks should immediately set up the Reducer and 
> RecordWriter and then call close on both since there are no inputs to the 
> reduce. I believe it should just work if we remove the check...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to