[
https://issues.apache.org/jira/browse/MAPREDUCE-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397041#comment-13397041
]
Robert Joseph Evans commented on MAPREDUCE-4351:
------------------------------------------------
MAPREDUCE-4256 Is trying to do something similar to this, but splitting the
resource monitoring up on a per resource basis. In light of that until we
decided how we want monitoring of different resources to look I would like to
see NM_CONTAINERS_MONITOR and ContainersMonitor marked as @Unstable. Just so
that it is obvious that these are likely to change in the future.
The rest of the patch looks good to me, but I have not dug into it in great
detail.
> Make ContainersMonitor pluggable
> --------------------------------
>
> Key: MAPREDUCE-4351
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4351
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv2, nodemanager
> Reporter: Andrew Ferguson
> Assignee: Andrew Ferguson
> Attachments: MAPREDUCE-4351-v1.patch, MAPREDUCE-4351-v2.patch,
> MAPREDUCE-4351-v3.patch
>
>
> Make the existing ContainersManager pluggable, just as the ContainerExecutor
> is currently. This will allow us to add container resource enforcement using
> other techniques (such as cgroups) in an extensible fashion.
--
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
