You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Iyappan Srinivasan (JIRA)" <ji...@apache.org> on 2010/04/05 09:21:27 UTC
[jira] Created: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
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: New Feature
Components: test
Affects Versions: 0.22.0
Reporter: Iyappan Srinivasan
Assignee: Iyappan Srinivasan
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.max.tracker.failures times, kill that task attempt id. After the mapred.max.tracker.failures 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.
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Iyappan Srinivasan (JIRA)" <ji...@apache.org>.
[ 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
Task Killing patch incorporating Ravi's comments.
> 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: New Feature
> Components: test
> Affects Versions: 0.22.0
> Reporter: Iyappan Srinivasan
> Assignee: Iyappan Srinivasan
> Attachments: 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.max.tracker.failures times, kill that task attempt id. After the mapred.max.tracker.failures 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.
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Iyappan Srinivasan (JIRA)" <ji...@apache.org>.
[ 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 scenario using herriot for TestTaskKilling scenario
> 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: New Feature
> Components: test
> Affects Versions: 0.22.0
> Reporter: Iyappan Srinivasan
> Assignee: Iyappan Srinivasan
> Attachments: 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.max.tracker.failures times, kill that task attempt id. After the mapred.max.tracker.failures 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.
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Iyappan Srinivasan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Vinay Kumar Thota (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858801#action_12858801 ]
Vinay Kumar Thota commented on MAPREDUCE-1671:
----------------------------------------------
I have some trivial comments and mainly on code formatting.
+ if(!taskInfo.isSetupOrCleanup()){ - Check the indentation, no spaces after 'if' and before '{'
TaskCompletionEvent[] taskCompletionEvents = jobClient.new
+ NetworkedJob(jInfo.getStatus()).getTaskCompletionEvents(0); - Check the indentation
+ if (count > 10)
+ Assert.fail("Since the task attemptid is not appearing in the" +
+ "TaskCompletionEvent, it seems this task attempt was not killed");
As per the java coding conventions the condition statements should always start and ends with braces even if it has one statement.
Should check all the places.
I could see indentation issue for continuation lines in many places.The continuation line should have 8 spaces from the statement where it started.
> 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, 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.
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Iyappan Srinivasan (JIRA)" <ji...@apache.org>.
[ 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
Thanks for the comments Cos. Incorporating it.
> 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, 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
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Iyappan Srinivasan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Iyappan Srinivasan updated MAPREDUCE-1671:
------------------------------------------
Description:
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.
was:
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.max.tracker.failures times, kill that task attempt id. After the mapred.max.tracker.failures times, the whole job should get killed.
> 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: New Feature
> Components: test
> Affects Versions: 0.22.0
> Reporter: Iyappan Srinivasan
> Assignee: Iyappan Srinivasan
> Attachments: 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.
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Iyappan Srinivasan (JIRA)" <ji...@apache.org>.
[ 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
Latest patch fixing some comments
> 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: New Feature
> Components: test
> Affects Versions: 0.22.0
> Reporter: Iyappan Srinivasan
> Assignee: Iyappan Srinivasan
> Attachments: 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.
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Iyappan Srinivasan (JIRA)" <ji...@apache.org>.
[ 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
Hi Vinay, Thanks for your comments. I have incorporated your comments in this patch, except for the last one. The spaces should be four from the previous line when a single line code continues to the next line. So, that comment I did not incorporate.
> 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, 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.
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Sharad Agarwal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sharad Agarwal updated MAPREDUCE-1671:
--------------------------------------
Affects Version/s: (was: 0.22.0)
Issue Type: Test (was: New Feature)
> 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: 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.
[jira] Commented: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Konstantin Boudnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854220#action_12854220 ]
Konstantin Boudnik commented on MAPREDUCE-1671:
-----------------------------------------------
I'm no expert in MR, however... is it possible that job never starts and this
{noformat}
+ LOG.info("Sleeping 5 seconds");
+ Thread.sleep(5000);
+ }
+ }
+ }
+ } while (!runningCount);
{noformat}
will continue indefinitely?
Otherwise it looks ok to me.
> 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: 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.
[jira] Commented: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Konstantin Boudnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856486#action_12856486 ]
Konstantin Boudnik commented on MAPREDUCE-1671:
-----------------------------------------------
Looking better. Now the comments for the code:
- is this an _official_ name to compare to jobIDs by {{toString()}} them and then run {{equals()}} on the result strings? Can't jobIDs be matches directly i.e. {{jobID1.equals(jobID2)}} or similar?
- If not then this seems like an excessive call to {{getID().toString()}}
{noformat}
+ //Temporarily store the jobid to use it later for comparison.
+ String jobidStore = rJob.getID().toString();
+ LOG.info("job id is :" + rJob.getID().toString());
{noformat}
- names {{client}} and {{wovenClient}} are in-descriptive. Perhaps {{jobClient}} and {{remoteJTClient}} will be a better choices? {{wovenClient}} implies a prerequisite knowledge about underlying AspectJ technology.
> 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
[jira] Commented: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Balaji Rajagopalan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856292#action_12856292 ]
Balaji Rajagopalan commented on MAPREDUCE-1671:
-----------------------------------------------
+1 looks good to me.
> 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: 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
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Iyappan Srinivasan (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Konstantin Boudnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Boudnik updated MAPREDUCE-1671:
------------------------------------------
Tags: herriot
> 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.
[jira] Commented: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Ravi Gummadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853718#action_12853718 ]
Ravi Gummadi commented on MAPREDUCE-1671:
-----------------------------------------
mapred.max.tracker.failures is not the config for making the job fail. You need to use mapreduce.map.maxattempts and mapreduce.reduce.maxattempts ?
> 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: New Feature
> Components: test
> Affects Versions: 0.22.0
> Reporter: Iyappan Srinivasan
> Assignee: Iyappan Srinivasan
> Attachments: 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.max.tracker.failures times, kill that task attempt id. After the mapred.max.tracker.failures 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.
[jira] Updated: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Iyappan Srinivasan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Iyappan Srinivasan updated MAPREDUCE-1671:
------------------------------------------
Attachment: (was: TestTaskKilling.patch)
> 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: New Feature
> Components: test
> Affects Versions: 0.22.0
> Reporter: Iyappan Srinivasan
> Assignee: Iyappan Srinivasan
> Attachments: 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.
[jira] Commented: (MAPREDUCE-1671) Test scenario for "Killing Task
Attempt id till job fails"
Posted by "Balaji Rajagopalan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856293#action_12856293 ]
Balaji Rajagopalan commented on MAPREDUCE-1671:
-----------------------------------------------
One minor comment java docs is missing.
> 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: 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