[
https://issues.apache.org/jira/browse/HADOOP-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreekanth Ramakrishnan updated HADOOP-4287:
-------------------------------------------
Attachment: HADOOP-4287-3.patch
Attaching the latest patch. The patch contains modified test case with
following:
- New Test case to check for Failing reduce.
- Test case now waits till all the tasks of the job have reported failures.
One thing to be noted is test case takes nearly _125 seconds_ to complete.
bq.Minor : You shouldn't catch and ignore any exception thrown by
RunningJob.runJob(). If something abnormal happens, let the test-case fail.
The reason why the exception is being caught is because when a Job fails
exception is thrown back from JobClient.runJob. We catch the exception to
continue working on the task counts.
> [mapred] jobqueue_details.jsp shows negative count of running and waiting
> reduces with CapacityTaskScheduler.
> -------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4287
> URL: https://issues.apache.org/jira/browse/HADOOP-4287
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Vinod K V
> Assignee: Sreekanth Ramakrishnan
> Priority: Blocker
> Attachments: HADOOP-4287-1.patch, HADOOP-4287-2.patch,
> HADOOP-4287-3.patch
>
>
> This I observed while running a job that always fails because of reduce
> failures. Need to investigate this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
