[
https://issues.apache.org/jira/browse/MAPREDUCE-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118072#comment-13118072
]
Robert Joseph Evans commented on MAPREDUCE-3050:
------------------------------------------------
The reason the patch is smaller and simpler is because in the first patch I
renamed SchedulerApp to SchedulerAppImpl. SchedulerApp is 20k so when the
patch deletes and adds back in the same code it adds 40k to the size of the
patch. If you want to change the names I can, it is not a big deal, but I
don't think that Scheduler*/Scheduler*Impl really indicate the design pattern
being used. I am not trying to separate out interface from implementation.
There is just one implementation and no place in the code to allow another one
to be inserted through configuration. I am just trying to expose a read only
subset of the information about this data structure. After making the change
to SchedulerNodeReport, I think it would be best to make the new interface
SchedulerAppReport as well. This fits in with the naming conventions used
elsewhere. I think I will upload a new patch with it changed to Report.
> 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,
> 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
