hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay Kumar Thota (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1646) Task Killing tests
Date Mon, 05 Apr 2010 09:09:27 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinay Kumar Thota updated MAPREDUCE-1646:
-----------------------------------------

    Attachment: TaskKilling_1646.patch

> Task Killing tests
> ------------------
>
>                 Key: MAPREDUCE-1646
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1646
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>          Components: test
>            Reporter: Vinay Kumar Thota
>            Assignee: Vinay Kumar Thota
>         Attachments: TaskKilling_1646.patch, TaskKilling_1646.patch, TaskKilling_1646.patch,
TEST-org.apache.hadoop.mapred.TestTaskKilling.txt
>
>
> 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.

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


Mime
View raw message