[
https://issues.apache.org/jira/browse/DRILL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426286#comment-16426286
]
ASF GitHub Bot commented on DRILL-143:
--------------------------------------
Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/1200
@Ben-Zvi / @paul-rogers
I discovered that the path `/cgroup` is unique only to my installation of
the package on CentOS. The standard path is `/sys/fs/cgroup`.
So, I've made changes that allow for users to specify the CGroups location.
Without this, the latest commit complains as expected:
```
[root@kk127 ~]#
/opt/mapr/drill/apache-drill-1.14.0-SNAPSHOT/bin/drillbit.sh restart
Stopping drillbit
..
Starting drillbit, logging to /var/log/drill/drillbit.out
ERROR: CGroup drillcpu not found. Ensure that daemon is running,
SYS_CGROUP_DIR is correctly set (currently, /sys/fs/cgroup ), and that the
CGroup exists
```
The `drill-env.sh` also specifies that the enforcement is only for CPU.
I'll put this in the documentation of the feature as well.
> 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)
