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

Scott Chen commented on MAPREDUCE-2198:
---------------------------------------

Hey Matei, Thanks for the review.

{quote}
How can you run the FairSchedulerShell from the command line? It doesn't seem 
to have a main method (so just using bin/hadoop 
org.apache.hadoop.mapred.FairSchedulerShell doesn't work), and I don't see it 
registered as a tool anywhere.
{quote}
It's my bad. I forgot to put a main method in FairSchedulerShell. I will update 
it.

{quote}
Will the slot counts set by the scheduler be visible in the JobTracker web UI? 
It looks like jobtracker.jsp looks at ClusterMetrics and machines.jsp looks at 
TaskTrackerStatus objects.
{quote}
For the ClusterMetircs, it's OK because we use TaskScheduler.getMaxSlots() to 
calculate the total slots in JobTracker. But you are right about machines.jsp. 
I should change it so that it also pulls the information from scheduler.


> Allow FairScheduler to control the number of slots on each TaskTracker
> ----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2198
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2198
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: contrib/fair-share
>    Affects Versions: 0.23.0
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2198.txt
>
>
> We can set the number of slots on the TaskTracker to be high and let 
> FairScheduler handles the slots.
> This approach allows us to change the number of slots on each node 
> dynamically.
> The administrator can change the number of slots with a CLI tool.
> One use case of this is for upgrading the MapReduce.
> Instead of restarting the cluster, we can run the new MapReduce on the same 
> cluster.
> And use the CLI tool to gradually migrate the slots.
> This way we don't lost the progress fo the jobs that's already executed.

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