[
https://issues.apache.org/jira/browse/MAPREDUCE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883442#action_12883442
]
Vinay Kumar Thota commented on MAPREDUCE-1794:
----------------------------------------------
{quote}
1) Since there is a change in restartClusterWithNewConfig now,
Hashtable<String,Object> prop should be used.
{quote}
Now we have implemented in generic fashion and there is no change is required
in the test. it accepts any type of data.
bq. 2) import java.util.Collection; - is not used anywhere.
removed the statement.
bq. 3) cleanup should be present in AfterClass also, just in case testcase
fails in the middle.
cleanup already there in after class.
> Test the job status of lost task trackers before and after the timeout.
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-1794
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1794
> Project: Hadoop Map/Reduce
> Issue Type: Task
> Components: test
> Reporter: Vinay Kumar Thota
> Assignee: Vinay Kumar Thota
> Attachments: 1794_lost_tasktracker.patch
>
>
> This test covers the following scenarios.
> 1. Verify the job status whether it is succeeded or not when the task
> tracker is lost and alive before the timeout.
> 2. Verify the job status and killed attempts of a task whether it is
> succeeded or not and killed attempts are matched or not when the task
> trackers are lost and it timeout for all the four attempts of a task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
