[MAPREDUCE-1646] Task Killing tests

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: test
• Assignee: Vinay Kumar Thota
• Reporter: Vinay Kumar Thota
• Created: 30/Mar/10 10:21
• Updated: 06/Aug/10 01:58

Description

The following tasks covered in the test.

1. In a running job, kill a task and verify the job succeeds.

2. Setup a job with long running tasks that write some output to HDFS. When one of the tasks is running, ensure that
the output/_temporary/_attempt-id directory is created. Kill the task. After the task is killed, make sure that the
output/_temporary/_attempt-id directory is cleaned up.

3. Setup a job with long running tasks that write some output to HDFS. When one of the tasks is running, ensure that
the output/_temporary/_attempt-id directory is created. Fail the task by simulating the map. After the task is failed,
make sure that the output/_temporary/_attempt-id directory is cleaned up. The important difference we are trying to
check is btw kill and fail, there would a subtle difference.

Issue Links

• is blocked by: MAPREDUCE-1774 Large-scale Automated Framework
• is required by: MAPREDUCE-1671 Test scenario for "Killing Task Attempt id till job fails"