[
https://issues.apache.org/jira/browse/DRILL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425028#comment-16425028
]
ASF GitHub Bot commented on DRILL-143:
--------------------------------------
Github user paul-rogers commented on a diff in the pull request:
https://github.com/apache/drill/pull/1200#discussion_r179025617
--- Diff: distribution/src/resources/drill-env.sh ---
@@ -86,6 +86,12 @@
#export DRILL_PID_DIR=${DRILL_PID_DIR:-$DRILL_HOME}
+# CGroup to which the Drillbit belong when running as a daemon using
--- End diff --
Also, maybe provide a bit more of a description. My guess is that the
CGroup must already be set up? That we only enforce CPU? Or, is what we enforce
determined entirely by what the user has configured? If so, wouldn't "drill" be
a better CGroup name?
> 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
> 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)
