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

Eric Payne commented on MAPREDUCE-3050:
---------------------------------------

@Bobby

I have a few questions:
* SchedulerAppImpl.java: IIUC, {{getReservedContainers()}} is new. It seems to 
be very similar to {{getAllReservedContainers()}}. Do we need both, and if so, 
how are they different?
* YarnScheduler.java: {{getApplication()}} is @Private, but the implementaion 
is public (CapacityScheduler, FifoScheduler). I thought Java complained when 
you do this? Why not just make the method interface @Public?. I guess the same 
question goes for {{getRootQueue()}}.
* {{getRootQueue()}}: The implementation of this method returns different types 
from CapacityScheduler vs. FifoScheduler. If I only have a reference to the 
YarnScheduler object (like in RMAppAttemptImpl), do I have to know whether it's 
a CapacityScheduler vs. FifoScheduler if I want to call {{getRootQueue()}}?

> 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
>
>         Attachments: MR-3050.txt
>
>
> 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