[ 
https://issues.apache.org/jira/browse/DRILL-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Rogers updated DRILL-4587:
-------------------------------
    Description: 
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 

  was:
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 two ways, depending on version.

$DRILL_HOME/conf/drill-env.sh allows the user to set environment variables that 
control the Drill launch. See the comment below for the list of these variables.

In Drill 1.7 and later, the administrator can set Drill configuration options 
directly on the launch command line in the form:

drillbit.sh start -Dvariable=value

For example, to control the control port:

drillbit.sh start -Ddrill.exec.http.port=8099 


> 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
>
> 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)

Reply via email to