[
https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iyappan Srinivasan updated MAPREDUCE-1671:
------------------------------------------
Attachment: TestTaskKilling.patch
TEST-org.apache.hadoop.mapred.TestTaskKilling.txt
Attaching the new patch and the logs, addressing Cos concerns and integrating
with the already existing TestTaskKilling file. That loop has a counter now
which will come out after 10 attempts, if the specific event did not happen.
Some more extra changes done are:
a) "client" and "wovenClient" are two objects which are declared again and
again in each testcase. So, generalised it on top.
b) One testcase (testDirCleanupAfterTaskFailed) was using maxAmpAttempts to 20,
which was making the job run even after the executuion has moved to the next
test. So, made it 1.
> 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: TEST-org.apache.hadoop.mapred.TestTaskKilling.txt,
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
