[
https://issues.apache.org/jira/browse/MAPREDUCE-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883473#action_12883473
]
Vinay Kumar Thota commented on MAPREDUCE-1899:
----------------------------------------------
bq. 2) FailMapper is not needed to be defined seperately as there is a
FailedMapper class already present in GenerateTaskChildProcess.java
FailedMapper is different with FailMapper. It creates the child process for a
mapper and then do the actions for failing.But FailMapper is simple mapper
which throws the exception apart from that nothing it will do.
bq. + while (!jInfo.getStatus().isJobComplete()) { +
UtilsForTests.waitFor(100); + jInfo = remoteJTClient.getJobInfo(jobId); + }
I will use the building block.
> [Herriot] Test jobsummary information for different jobs.
> ---------------------------------------------------------
>
> Key: MAPREDUCE-1899
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1899
> Project: Hadoop Map/Reduce
> Issue Type: Task
> Components: test
> Reporter: Vinay Kumar Thota
> Assignee: Vinay Kumar Thota
> Attachments: 1899-ydist-security.patch
>
>
> Test the following scenarios.
> 1. Verify the job summary information for killed job.
> 2. Verify the job summary information for failed job.
> 3. Verify the job queue information in job summary after job has successfully
> completed.
> 4. Verify the job summary information for high ram jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
