[
https://issues.apache.org/jira/browse/MAPREDUCE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767768#action_12767768
]
Iyappan Srinivasan commented on MAPREDUCE-1048:
-----------------------------------------------
+1 from QA on reservation.
Ran some reservation specific jobs:
1) In a 8 node cluster, Run a normal job which takes up 7 slots. Then, run a
high RAM job, which takes up 3 slots for 1 map. This will cause this high RAM
job to reserve the extra 1 slot and wait, since it needs the other 2 slots to
start running. At this point
a) Kill a Task tracker which has that 1 reserved slot and make it lost. The
reserved slot should dissapear.
b) Kill task tracker and start it again. It should again get that 1
reservation.
c) Blacklist that tasktracker. The reservation status should reflect
accordingly. Bring back the node to healthy state.The reservation status should
reflect accordingly
d) Decomission that tasktracker. The reservation status should reflect
accordingly. Bring back the node to healthy state.The reservation status should
reflect accordingly.
> Show total slot usage in cluster summary on jobtracker webui
> ------------------------------------------------------------
>
> Key: MAPREDUCE-1048
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1048
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker
> Affects Versions: 0.20.1
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.22.0
>
> Attachments: mapred-1048-v1.0.patch, mapred-1048-v1.1.patch,
> patch-1048-0.20.txt, patch-1048-1.txt, patch-1048-2.txt, patch-1048-3.txt,
> patch-1048-4.txt, patch-1048-5.txt, patch-1048-6.txt, patch-1048-ydist.txt,
> patch-1048.txt
>
>
> With High-Ram jobs coming into the picture, its important to also show the
> slot usage in cluster summary since total-running-maps <
> total-slots-occupied.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
