[
https://issues.apache.org/jira/browse/DRILL-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228902#comment-15228902
]
Paul Rogers edited comment on DRILL-4587 at 4/6/16 8:31 PM:
------------------------------------------------------------
User-settable environment variables:
DRILL_CONF_DIR Alternate drill conf dir. Default is $DRILL_HOME/conf.
DRILL_LOG_DIR Where log files are stored. Default is /var/log/drill if
that exists, else $DRILL_HOME/log
DRILL_PID_DIR The pid files are stored. /tmp by default.
DRILL_IDENT_STRING A string representing this instance of drillbit. $USER by
default
DRILL_NICENESS The scheduling priority for daemons. Defaults to 0.
DRILL_STOP_TIMEOUT Time, in seconds, after which we kill -9 the server if it
has not stopped. Default 120 seconds.
DRILL_HOME Drill home (defaults based on this script's path.)
JAVA_HOME The java implementation to use.
DRILL_CLASSPATH Extra Java CLASSPATH entries.
DRILL_CLASSPATH_PREFIX Extra Java CLASSPATH entries that should be prefixed
to the system classpath.
HADOOP_HOME Hadoop home
HBASE_HOME HBase home
LOG_OPTS ??
DRILL_JAVA_OPTS Optional JVM arguments such as system property overides
used by both the drillbit and client.
DRILLBIT_JAVA_OPTS Optional JVM arguments specifically for the drillbit.
SERVER_GC_OPTS todo
was (Author: paul-rogers):
User-settable environment variables:
DRILL_CONF_DIR Alternate drill conf dir. Default is
${DRILL_HOME}/conf.
DRILL_LOG_DIR Where log files are stored. Default is /var/log/drill if
that exists, else $DRILL_HOME/log
DRILL_PID_DIR The pid files are stored. /tmp by default.
DRILL_IDENT_STRING A string representing this instance of drillbit. $USER by
default
DRILL_NICENESS The scheduling priority for daemons. Defaults to 0.
DRILL_STOP_TIMEOUT Time, in seconds, after which we kill -9 the server if it
has not stopped. Default 120 seconds.
DRILL_HOME Drill home (defaults based on this script's path.)
JAVA_HOME The java implementation to use.
DRILL_CLASSPATH Extra Java CLASSPATH entries.
DRILL_CLASSPATH_PREFIX Extra Java CLASSPATH entries that should be prefixed
to the system classpath.
HADOOP_HOME Hadoop home
HBASE_HOME HBase home
LOG_OPTS ??
DRILL_JAVA_OPTS Optional JVM arguments such as system property overides
used by both the drillbit and client.
DRILLBIT_JAVA_OPTS Optional JVM arguments specifically for the drillbit.
SERVER_GC_OPTS todo
> Document Drillbit launch options
> --------------------------------
>
> Key: DRILL-4587
> URL: https://issues.apache.org/jira/browse/DRILL-4587
> Project: Apache Drill
> Issue Type: Improvement
> Components: Documentation
> Reporter: Paul Rogers
> Assignee: Bridget Bevens
>
> Drill provides the drillbit.sh script to launch Drill. When Drill is run in
> production environments, or when managed by a tool such as Mesos or YARN,
> customers have many options to customize the launch options. We should
> document this information as below.
> The user can configure Drill launch in one of four ways, depending on their
> needs.
> 1. Using the properties in drill-override.conf. Sets only startup and runtime
> properties. All drillbits should use a copy of the file so that properties
> set here apply to all drill bits and to client applications.
> 2. By setting environment variables prior to launching Drill. See the list
> below. Use this to customize properties per drill-bit, such as for setting
> port numbers. This option is useful when launching Drill from a tool such as
> Mesos or YARN.
> 3. By setting environment variables in $DRILL_HOME/conf/drill-env.sh. See the
> list below. This script is intended to be unique to each node and is another
> way to customize properties for this one node.
> 4. In Drill 1.7 and later, the administrator can set Drill configuration
> options directly on the launch command as shown below. This option is also
> useful when launching Drill from a tool such as YARN or Mesos. Options are of
> the form:
> drillbit.sh start -Dvariable=value
> For example, to control the HTTP port:
> drillbit.sh start -Ddrill.exec.http.port=8099
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
