[
https://issues.apache.org/jira/browse/DRILL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452696#comment-16452696
]
ASF GitHub Bot commented on DRILL-143:
--------------------------------------
Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/1239
@kkhatua, it turns out that upstream YARN has long had effective cgroup
support per container. ( have the pleasure of sitting near the guy who
maintains that work.)There has long been a discussion about whether the MapR
version of YARN picked up those changes, we believe that MapR does *not*
support this upstream work.
As a result, under Apache YARN, the YARN NM itself will impose cgroup
controls and Drill need not do it itself. For MapR YARN (only) Drill (and all
other YARN apps) must do their own cgroup control.
Please make sure that this feature is off by default to allow YARN to do
the work. Only enable it for versions of YARN (such as MapR) which do not
provide cgroup control in YARN itself.
> Support CGROUPs resource management
> -----------------------------------
>
> Key: DRILL-143
> URL: https://issues.apache.org/jira/browse/DRILL-143
> Project: Apache Drill
> Issue Type: New Feature
> Reporter: Jacques Nadeau
> Assignee: Kunal Khatua
> Priority: Major
> Labels: doc-impacting, ready-to-commit
> Fix For: 1.14.0
>
> Attachments: 253ce178-ddeb-e482-cd64-44ab7284ad1c.sys.drill
>
>
> For the purpose of playing nice on clusters that don't have YARN, we should
> write up configuration and scripts to allows users to run Drill next to
> existing workloads without sharing resources.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
