drill-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tshi...@apache.org
Subject [11/19] drill git commit: minor edits
Date Mon, 04 May 2015 15:48:03 GMT
minor edits


Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/1d09c83a
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/1d09c83a
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/1d09c83a

Branch: refs/heads/gh-pages
Commit: 1d09c83a95221c79601a55f02c1690436e5803de
Parents: 3d8b93d
Author: Kristine Hahn <khahn@maprtech.com>
Authored: Mon May 4 06:08:24 2015 -0700
Committer: Kristine Hahn <khahn@maprtech.com>
Committed: Mon May 4 06:08:24 2015 -0700

----------------------------------------------------------------------
 _docs/manage-drill/030-start-stop.md | 34 +++++++++++++++++++++++--------
 1 file changed, 25 insertions(+), 9 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/1d09c83a/_docs/manage-drill/030-start-stop.md
----------------------------------------------------------------------
diff --git a/_docs/manage-drill/030-start-stop.md b/_docs/manage-drill/030-start-stop.md
index 8e276c7..51a18b2 100644
--- a/_docs/manage-drill/030-start-stop.md
+++ b/_docs/manage-drill/030-start-stop.md
@@ -2,11 +2,18 @@
 title: "Starting/Stopping Drill"
 parent: "Manage Drill"
 ---
-How you start Drill depends on the installation method you followed. If you installed Drill
in embedded mode, invoking SQLLine automatically starts a Drillbit locally. If you installed
Drill in distributed mode on a MapR cluster, the installation process starts the Drillbit
service automatically; otherwise,  you must start the Drillbit service before invoking running
queries.
+How you start Drill depends on the installation method you followed. If you installed Drill
in embedded mode, invoking SQLLine automatically starts a Drillbit locally. 
+
+On a MapR cluster, Drill runs as a service and the installation process starts the Drillbit
service automatically. If you installed Drill in distributed mode, and the Drillbit on a node
did not start, start the Drillbit before invoking running queries.
+
 
 ## Controlling a Drillbit
 
-Using the **drillbit command**, located in the `bin` directory, check the status of, start,
start, and restart a DrillBit. You can use a configuration file to start Drill. Using such
a file is handy for controlling Drillbits on multiple nodes.
+The Drillbit service accepts requests from the client, processing the queries, and returning
results to the client. You install Drill as a service and run the Drillbit on all of the required
nodes in a Hadoop cluster to form a distributed cluster environment. When a Drillbit runs
on each data node in the cluster, Drill maximizes data locality during query execution. Movement
of data over the network or between nodes is minimized or eliminated when possible.
+
+If you use Drill in distributed mode, you need to understand how to control a Drillbit. If
you use Drill in embedded mode, you do not use the Drillbit command. Windows and Mac OS X
run Drill only in embedded mode, and therefore do not use the Drillbit command.
+
+Using the **drillbit command**, located in the `bin` directory, you check the status of the
Drillbit, start, stop, and restart a DrillBit. You can use a configuration file to start Drill.
Using such a file is handy for controlling Drillbits on multiple nodes.
 
 ### drillbit Command Syntax
 
@@ -18,9 +25,10 @@ For example, to restart a Drillbit, navigate to the Drill installation
directory
 
 ## Invoking SQLLine
 SQLLine is used as the Drill shell. SQLLine connects to relational databases and executes
SQL commands. You invoke SQLLine for Drill in embedded or distributed mode. If you want to
use a particular storage plugin, you can indicate the schema name when you invoke SQLLine.
-To start SQLLine, use the following **sqlline command** syntax:
 
 ### SQLLine Command Syntax
+To start SQLLine, use the following **sqlline command** syntax:
+
 
     sqlline –u jdbc:drill:[schema=<storage plugin>;]zk=<zk name>[:<port>][,<zk
name2>[:<port>]... ]
 
@@ -28,16 +36,21 @@ To start SQLLine, use the following **sqlline command** syntax:
 
 * `-u` is the option that precedes a connection string. Required.  
 * `jdbc` is the connection protocol. Required.  
-* `schema` is the name of a storage plugin to use for queries. Optional.  
-* `Zk=zkname` is one or more zookeeper host names or IP addresses. Required.  
+* `schema` is the name of a [storage plugin]({{site.baseurl}}/docs/storage-plugin-registration)
to use for queries. Optional.  
+* `Zk=zkname` is one or more zookeeper host names or IP addresses, or the keyword `local`,
which is an alias for localhost. Required.  
 * `port` is the zookeeper port number. Optional. Port 2181 is the default.  
 
 ## Examples of Starting Drill
-Issue the sqlline command from the Drill installation directory. For example, this command
starts Drill on an embedded mode (single-node) cluster:
+Issue the **sqlline** command from the Drill installation directory. The simplest example
of how to start SQLLine is to identify the protocol, JDBC, and zookeeper node or nodes in
the **sqlline** command. This example starts SQLLine on a node in an embedded, single-node
cluster:
+
+    sqlline -u jdbc:drill:zk=local
+
+This example also starts SQLLine in embedded mode using the `dfs` storage plugin. Specifying
the storage plugin when you start up eliminates the need to specify the storage plugin in
the query:
+
 
     bin/sqlline –u jdbc:drill:schema=dfs;zk=localhost
 
-This command starts Drill on a distributed mode (multi-node) cluster configured to run zookeeper
on three nodes:
+This command starts SQLLine in distributed, (multi-node) mode in a cluster configured to
run zookeeper on three nodes:
 
     bin/sqlline –u jdbc:drill:zk=cento23,zk=centos24,zk=centos26:5181
 
@@ -49,8 +62,11 @@ To exit SQLLine, issue the following command:
 
 ## Stopping Drill
 
-In some cases, such as stopping while a query is in progress, the `!quit` command does not
stop Drill. You need to kill the Drill process. For example, on Mac OS X and Linux, follow
-these steps:
+In some cases, such as stopping while a query is in progress, the `!quit` command does not
stop Drill running in embedded mode. In distributed mode, you stop the Drillbit service instead
of killing the Drillbit process. 
+
+To stop the Drill process on Mac OS X and Linux, use the kill command. On Windows, use the
**TaskKill** command.
+
+For example, on Mac OS X and Linux, follow these steps:
 
   1. Issue a CTRL Z to stop the query, then start Drill again. If the startup message indicates
success, skip the rest of the steps. If not, proceed to step 2.
   2. Search for the Drill process IDs.


Mime
View raw message