hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iyappan Srinivasan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task Attempt id till job fails"
Date Wed, 04 Aug 2010 07:58:16 GMT

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

Iyappan Srinivasan updated MAPREDUCE-1671:
------------------------------------------

    Attachment: 1671-ydist-security-patch.txt

resolving timing issues and interdependency with other testcase issue, when running in the
secured cluster.

> Test scenario for "Killing Task Attempt id till job fails"
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-1671
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1671
>             Project: Hadoop Map/Reduce
>          Issue Type: Test
>          Components: test
>            Reporter: Iyappan Srinivasan
>            Assignee: Iyappan Srinivasan
>         Attachments: 1671-ydist-security-patch.txt, TEST-org.apache.hadoop.mapred.TestTaskKilling.txt,
TestTaskKilling.patch, TestTaskKilling.patch, TestTaskKilling.patch, TestTaskKilling.patch,
TestTaskKilling.patch
>
>
> 1) In a  job, kill the task attemptid of one task.  Whenever that task  tries to run
again with another task atempt id for mapred.map.max.attempts times, kill that task attempt
id. After the mapred.map.max.attempts times, the whole job should get killed.

-- 
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