[
https://issues.apache.org/jira/browse/YARN-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved YARN-4.
----------------------------------------
Resolution: Won't Fix
Went through the patch. It seems like this was originally created for
CPU-isolation. But with YARN-3, we have taken a completely different approach
(creating cgroups instead of active monitoring). ContainersMonitor is largely
just used for memory-monitoring, so there is little value in making it an
abstraction.
Closing this as Won't Fix for now. [~adferguson], please reopen this if you
disagree.
> Make ContainersMonitor pluggable
> --------------------------------
>
> Key: YARN-4
> URL: https://issues.apache.org/jira/browse/YARN-4
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Andrew Ferguson
> Attachments: MAPREDUCE-4351-v1.patch, MAPREDUCE-4351-v2.patch,
> MAPREDUCE-4351-v3.patch, MAPREDUCE-4351-v4.patch, MAPREDUCE-4351-v4.patch,
> MAPREDUCE-4351-v5.patch, MAPREDUCE-4351-v5.patch, MAPREDUCE-4351-v6.patch,
> MAPREDUCE-4351-v7.patch, MAPREDUCE-4351-v7.sh
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
