[ 
https://issues.apache.org/jira/browse/MAPREDUCE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729165#action_12729165
 ] 

Iyappan Srinivasan commented on MAPREDUCE-467:
----------------------------------------------

Additional testing done mainly on Jobtracker restart, TT restart and 
blacklisting. All testacses are found to pass:

1) If a tasktracker is globally blacklisted, that tasktracker should not  
capture any more tasks. After coming out fo blacklisting after 24 hours, it 
should again start accepting tasks and increasing the task nubmers in its 
windows. : Pass

2) After restarting a blacklisted tasktracker, it shd be made healthy and 
continue to receive task numbers. - In 5 node cluster. :Pass

3) Killing a task tracker and also suspending a task tracker. - Killing a task 
tracker and restarting a tasktracker takes off all the information. Suspending 
and continuing with task tracker retains the information.In both scenarios they 
continue to receive task numbers after coming bacl to healthy mode. : Pass

3) JT is supended and brought back. - The task number windows are still 
retained.: Pass

4) Jt restart at differnt scenarios :
   a) When at least 3 tasks are waiting.   b) When file size of a  task is 
zero.   c) After some jobs are completed.    d) When it is two times restarted. 
  e) When a  job is 20% complete, when a job is 50% complete. - After job 
tracker restarts, all the information of the connected tasktracker, goes off. 
At this point the job.persist is true.

5) TT is suspended and brought back. Still  numbers shd be captured : pass

6) When different tasks are run at the same time. -Different task tracker 
windows is able to capture correct numbers. : pass

7) Kill a  task tracker and rejoin it. It shd work. - works, but previous task 
succeded info gone.

8) Run jobs with different priorities and then check if is captured properly. 
Also restart JT in this scenario and check if the job is restarted properly. : 
Pass

9) Changing job priority dynamically. How will it affect the task tracker's 
capture of tasks. -It captures it normally

10) In job level blacklisting scenario, tasks are continuign to be received.


> Collect information about number of tasks succeeded / total per time unit for 
> a tasktracker. 
> ---------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-467
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-467
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Hemanth Yamijala
>            Assignee: Sharad Agarwal
>         Attachments: 467_v4.patch, 467_v5.patch, 467_v6.patch, 5931_v1.patch, 
> 5931_v2.patch, 5931_v3.patch
>
>
> Collecting information of number of tasks succeeded / total per tasktracker 
> and being able to see these counts per hour, day and since start time will 
> help reason about things like the blacklisting strategy.

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

Reply via email to