[
https://issues.apache.org/jira/browse/DRILL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452883#comment-16452883
]
ASF GitHub Bot commented on DRILL-143:
--------------------------------------
Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/1239
One other thing to highlight from an earlier comment. CPU is something that
the user specifies in the DoY config file. That information is passed to YARN
in container requests. This feature asks the user to modify the drill-env.sh
file to enable cgroups to limit CPU. As a result, the user must specify the CPU
limit in two places.
DoY went to extreme lengths to unify memory configuration so it is set in
one place. The assumption was that, since Apache YARN handles cgroups, we've
also got unified CPU specification. But, in this "side-car" approach we don't.
So, would be good to capture the CPU amount from the YARN config as explained
earlier and use that to set the Drill cgroups env vars -- but only if some
"self-enforcing cgroup" flag is enabled in the config (which can be done by
default for the limited MapR YARN.)
> 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
> 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)
