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

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

I will upmerge the patch.  The reason for the split between SchedulerApp 
interface and SchedulerAppImpl is that SchedulerAppImpl seemed to expose way 
too many methods that should be specific to the scheduler.  I wanted something 
that was read only that could not be used to accidentally manipulate the 
scheduler.  I named them badly though.  I will rename the interface to 
SchedulerAppInfo and the class back to SchedulerApp.  I will look at 
SchedulerNode and see if it should take a SchedulerApp.
                
> 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: mrv2, 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, MR-3050.txt, MR-3050.txt, 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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to