[
https://issues.apache.org/jira/browse/DRILL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423552#comment-16423552
]
ASF GitHub Bot commented on DRILL-143:
--------------------------------------
GitHub user kkhatua opened a pull request:
https://github.com/apache/drill/pull/1200
DRILL-143: Support CGROUPs resource management
Introduces the `DRILLBIT_CGROUP` option in defined in `drill-env.sh`
The startup script checks if the specified CGroup (ver 2) is available and
tries to apply it to the launched Drillbit JVM.
This would benefit not just Drill-on-YARN usecases, but any setup that
would like CGroups for enforcement of (cpu) resources management.
e.g when Drillbit is configured to use `drillcpu` cgroup
```
[root@maprlabs ~]#
/opt/mapr/drill/apache-drill-1.14.0-SNAPSHOT/bin/drillbit.sh restart
Stopping drillbit
..
Starting drillbit, logging to /var/log/drill/drillbit.out
WARN: Drillbit's CPU resource usage will be managed under the CGroup :
drillcpu (up to 4.00 cores allowed)
```
e.g. Non-existent CGroup `droolcpu` is used
```
[root@maprlabs ~]#
/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 droolcpu does not found. Ensure that daemon is running and
cgroup exists
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kkhatua/drill DRILL-143
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/1200.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1200
----
commit e9a2551b315b4395c5227dad017f2b4340f41108
Author: Kunal Khatua <kkhatua@...>
Date: 2018-04-03T05:35:53Z
DRILL-143: Support CGROUPs resource management
Introduces the DRILLBIT_CGROUP option in drill-env.sh.
The startup script checks if the specified CGroup (ver 2) is available and
tries to apply it to the launched Drillbit JVM.
This would benefit not just Drill-on-YARN usecases, but any setup that
would like CGroups for enforcement of (cpu) resources management.
e.g when Drillbit is configured to use `drillcpu` cgroup
```
[root@maprlabs ~]#
/opt/mapr/drill/apache-drill-1.14.0-SNAPSHOT/bin/drillbit.sh restart
Stopping drillbit
..
Starting drillbit, logging to /var/log/drill/drillbit.out
WARN: Drillbit's CPU resource usage will be managed under the CGroup :
drillcpu (up to 4.00 cores allowed)
```
e.g. Non-existent CGroup `droolcpu` is used
```
[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 droolcpu does not found. Ensure that daemon is running and
cgroup exists
```
----
> 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
>
>
> 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)
