[
https://issues.apache.org/jira/browse/MAPREDUCE-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397773#comment-13397773
]
Arun C Murthy commented on MAPREDUCE-4351:
------------------------------------------
I'm sorry to come in late...
I'm a little confused by this approach, so please bear with me.
It seems to me that ContainersMonitory should actually go away once we goto
cgroups etc., since the cgroup itself would 'box' the process in, there-by
removing the need for any monitoring from NodeManager. If so, this would be not
required at all?
Thus, once we go via the cgroups route, the LCE should do the necessary work to
put the process in the cgroup. This means that we will need different
*versions* of LCE for rhel5/centos5, rhel6/centos6 etc.
> 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, MAPREDUCE-4351-v4.patch, MAPREDUCE-4351-v4.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
