[
https://issues.apache.org/jira/browse/DRILL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452872#comment-16452872
]
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/1239#discussion_r184169114
--- Diff: distribution/src/resources/yarn-drillbit.sh ---
@@ -175,4 +209,11 @@ fi
echo "`date` Starting drillbit on `hostname` under YARN, logging to
$DRILLBIT_LOG_PATH"
echo "`ulimit -a`" >> "$DRILLBIT_LOG_PATH" 2>&1
-"$DRILL_HOME/bin/runbit" exec
+# Run in background
+"$DRILL_HOME/bin/runbit" exec &
--- End diff --
Under YARN, it is YARN that maintains the pid, not Drill. YARN expects its
child processes to run in the foreground and will handle capturing the pid.
This is a case in which "native" Apache YARN works differently than "MapR
YARN." Since Apache YARN handles cgroups, it is the one that needs the pid.
Under MapR's limited YARN, then Drill is second-guessing YARN and needs the
pid. It may be that MapR's YARN can handle a background process; I don't recall
the details.
Is there way way to run Drill in the background, get the pid, then return
to the foreground so that the script does not exit until Drill itself exits?
In fact, if I remember correctly, the scripts have two layers; in one
layer, the script replaces itself with the Drill process. Something to check.
> 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)
