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

Robert Joseph Evans commented on MAPREDUCE-3050:
------------------------------------------------

OK so to summarize the data that is needed is the following:

   * Total applications submitted since restart. 
   * Total number of containers running.
   * Total memory(Resource) usage for running containers.
   * Total capacity memory(Resource) of the cluster.
   * Total memory(Resource) reserved in the cluster.
   * Given an ApplicationAttemptId get the 
      ** Containers for that attempt
      ** Current resource utilization for that attempt
      ** Current reserved resources for that attempt
   * Given a NodeId get the
      ** Number of containers on the node
      ** Memory (Resource) used
      ** Memory (Resource) available 

@Ravi I don't think there is any way for the RM to get the no of maps and the 
number of reduces because that is Map/Reduce specific and you should be talking 
to the AppMaster/HistoryServer for that information.


> YarnScheduler needs to expose Resource Usage Information
> --------------------------------------------------------
>
>                 Key: MAPREDUCE-3050
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3050
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Blocker
>             Fix For: 0.23.0, 0.24.0
>
>
> Before the recent refactor The nodes had information in them about how much 
> resources they were using.  This information is not hidden inside 
> SchedulerNode.  Similarly resource usage information about an application, or 
> in aggregate is only available through the Scheduler and there is not 
> interface to pull it out.
> We need to expose APIs to get Resource and Container information from the 
> scheduler, in aggregate across the entire cluster, per application, per node, 
> and ideally also per queue if applicable (although there are no JIRAs I am 
> aware of that need this right now).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to