You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@drill.apache.org by ts...@apache.org on 2015/05/19 01:36:52 UTC
[29/31] drill git commit: add BB's log and debug,
using jdbc > using jdbc with squirrel on win
add BB's log and debug, using jdbc > using jdbc with squirrel on win
Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/134b6ff8
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/134b6ff8
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/134b6ff8
Branch: refs/heads/gh-pages
Commit: 134b6ff8e90ea689abad9819b071cd9235c07877
Parents: e331872
Author: Kristine Hahn <kh...@maprtech.com>
Authored: Mon May 18 16:27:32 2015 -0700
Committer: Kristine Hahn <kh...@maprtech.com>
Committed: Mon May 18 16:27:32 2015 -0700
----------------------------------------------------------------------
_data/docs.json | 314 ++++++++++++++++---
_docs/073-log-and-debug.md | 3 +
.../001-log-and-debug-introduction.md | 15 +
_docs/log-and-debug/002-error-messages.md | 25 ++
_docs/log-and-debug/003-modify-logback.xml.md | 54 ++++
.../004-review-the-java-stack-trace.md | 41 +++
.../020-using-jdbc-with-squirrel-on-windows.md | 164 ++++++++++
_docs/odbc-jdbc-interfaces/020-using-jdbc.md | 164 ----------
.../sql-functions/073-log-and-debug.md | 3 +
9 files changed, 583 insertions(+), 200 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/drill/blob/134b6ff8/_data/docs.json
----------------------------------------------------------------------
diff --git a/_data/docs.json b/_data/docs.json
index 7fa1345..6566216 100644
--- a/_data/docs.json
+++ b/_data/docs.json
@@ -2805,6 +2805,23 @@
"title": "Enron Emails",
"url": "/docs/enron-emails/"
},
+ "Error Messages": {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "Modify logback.xml",
+ "next_url": "/docs/modify-logback-xml/",
+ "parent": "Log and Debug",
+ "previous_title": "Log and Debug Introduction",
+ "previous_url": "/docs/log-and-debug-introduction/",
+ "relative_path": "_docs/log-and-debug/002-error-messages.md",
+ "title": "Error Messages",
+ "url": "/docs/error-messages/"
+ },
"FLATTEN": {
"breadcrumbs": [
{
@@ -3660,8 +3677,8 @@
}
],
"children": [],
- "next_title": "Using JDBC",
- "next_url": "/docs/using-jdbc/",
+ "next_title": "Using JDBC with SQuirreL on Windows",
+ "next_url": "/docs/using-jdbc-with-squirrel-on-windows/",
"parent": "ODBC/JDBC Interfaces",
"previous_title": "ODBC/JDBC Interfaces",
"previous_url": "/docs/odbc-jdbc-interfaces/",
@@ -3952,6 +3969,104 @@
"title": "Lexical Structure",
"url": "/docs/lexical-structure/"
},
+ "Log and Debug": {
+ "breadcrumbs": [],
+ "children": [
+ {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "Error Messages",
+ "next_url": "/docs/error-messages/",
+ "parent": "Log and Debug",
+ "previous_title": "Log and Debug",
+ "previous_url": "/docs/log-and-debug/",
+ "relative_path": "_docs/log-and-debug/001-log-and-debug-introduction.md",
+ "title": "Log and Debug Introduction",
+ "url": "/docs/log-and-debug-introduction/"
+ },
+ {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "Modify logback.xml",
+ "next_url": "/docs/modify-logback-xml/",
+ "parent": "Log and Debug",
+ "previous_title": "Log and Debug Introduction",
+ "previous_url": "/docs/log-and-debug-introduction/",
+ "relative_path": "_docs/log-and-debug/002-error-messages.md",
+ "title": "Error Messages",
+ "url": "/docs/error-messages/"
+ },
+ {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "Review the Java Stack Trace",
+ "next_url": "/docs/review-the-java-stack-trace/",
+ "parent": "Log and Debug",
+ "previous_title": "Error Messages",
+ "previous_url": "/docs/error-messages/",
+ "relative_path": "_docs/log-and-debug/003-modify-logback.xml.md",
+ "title": "Modify logback.xml",
+ "url": "/docs/modify-logback-xml/"
+ },
+ {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "",
+ "next_url": "",
+ "parent": "Log and Debug",
+ "previous_title": "Modify logback.xml",
+ "previous_url": "/docs/modify-logback-xml/",
+ "relative_path": "_docs/log-and-debug/004-review-the-java-stack-trace.md",
+ "title": "Review the Java Stack Trace",
+ "url": "/docs/review-the-java-stack-trace/"
+ }
+ ],
+ "next_title": "Log and Debug Introduction",
+ "next_url": "/docs/log-and-debug-introduction/",
+ "parent": "",
+ "previous_title": "Project Bylaws",
+ "previous_url": "/docs/project-bylaws/",
+ "relative_path": "_docs/sql-reference/sql-functions/073-log-and-debug.md",
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ },
+ "Log and Debug Introduction": {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "Error Messages",
+ "next_url": "/docs/error-messages/",
+ "parent": "Log and Debug",
+ "previous_title": "Log and Debug",
+ "previous_url": "/docs/log-and-debug/",
+ "relative_path": "_docs/log-and-debug/001-log-and-debug-introduction.md",
+ "title": "Log and Debug Introduction",
+ "url": "/docs/log-and-debug-introduction/"
+ },
"MapR-DB Format": {
"breadcrumbs": [
{
@@ -3990,6 +4105,23 @@
"title": "Math and Trig",
"url": "/docs/math-and-trig/"
},
+ "Modify logback.xml": {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "Review the Java Stack Trace",
+ "next_url": "/docs/review-the-java-stack-trace/",
+ "parent": "Log and Debug",
+ "previous_title": "Error Messages",
+ "previous_url": "/docs/error-messages/",
+ "relative_path": "_docs/log-and-debug/003-modify-logback.xml.md",
+ "title": "Modify logback.xml",
+ "url": "/docs/modify-logback-xml/"
+ },
"MongoDB Plugin for Apache Drill": {
"breadcrumbs": [
{
@@ -4200,8 +4332,8 @@
}
],
"children": [],
- "next_title": "Using JDBC",
- "next_url": "/docs/using-jdbc/",
+ "next_title": "Using JDBC with SQuirreL on Windows",
+ "next_url": "/docs/using-jdbc-with-squirrel-on-windows/",
"parent": "ODBC/JDBC Interfaces",
"previous_title": "ODBC/JDBC Interfaces",
"previous_url": "/docs/odbc-jdbc-interfaces/",
@@ -4222,9 +4354,9 @@
"parent": "ODBC/JDBC Interfaces",
"previous_title": "Interfaces Introduction",
"previous_url": "/docs/interfaces-introduction/",
- "relative_path": "_docs/odbc-jdbc-interfaces/020-using-jdbc.md",
- "title": "Using JDBC",
- "url": "/docs/using-jdbc/"
+ "relative_path": "_docs/odbc-jdbc-interfaces/020-using-jdbc-with-squirrel-on-windows.md",
+ "title": "Using JDBC with SQuirreL on Windows",
+ "url": "/docs/using-jdbc-with-squirrel-on-windows/"
},
{
"breadcrumbs": [
@@ -4406,8 +4538,8 @@
"next_title": "ODBC on Linux and Mac Introduction",
"next_url": "/docs/odbc-on-linux-and-mac-introduction/",
"parent": "ODBC/JDBC Interfaces",
- "previous_title": "Using JDBC",
- "previous_url": "/docs/using-jdbc/",
+ "previous_title": "Using JDBC with SQuirreL on Windows",
+ "previous_url": "/docs/using-jdbc-with-squirrel-on-windows/",
"relative_path": "_docs/odbc-jdbc-interfaces/030-using-odbc-on-linux-and-mac-os-x.md",
"title": "Using ODBC on Linux and Mac OS X",
"url": "/docs/using-odbc-on-linux-and-mac-os-x/"
@@ -4709,8 +4841,8 @@
}
],
"children": [],
- "next_title": "Query Audit Logging",
- "next_url": "/docs/query-audit-logging/",
+ "next_title": "Log and Debug",
+ "next_url": "/docs/log-and-debug/",
"parent": "Performance Tuning",
"previous_title": "Performance Tuning",
"previous_url": "/docs/performance-tuning/",
@@ -4736,8 +4868,8 @@
}
],
"children": [],
- "next_title": "Query Audit Logging",
- "next_url": "/docs/query-audit-logging/",
+ "next_title": "Log and Debug",
+ "next_url": "/docs/log-and-debug/",
"parent": "Performance Tuning",
"previous_title": "Performance Tuning",
"previous_url": "/docs/performance-tuning/",
@@ -4858,8 +4990,8 @@
"Project Bylaws": {
"breadcrumbs": [],
"children": [],
- "next_title": "",
- "next_url": "",
+ "next_title": "Log and Debug",
+ "next_url": "/docs/log-and-debug/",
"parent": "",
"previous_title": "2014 Q1 Drill Report",
"previous_url": "/docs/2014-q1-drill-report/",
@@ -4891,8 +5023,8 @@
"next_title": "Getting Query Information",
"next_url": "/docs/getting-query-information/",
"parent": "",
- "previous_title": "Performance Tuning Introduction",
- "previous_url": "/docs/performance-tuning-introduction/",
+ "previous_title": "Log and Debug",
+ "previous_url": "/docs/log-and-debug/",
"relative_path": "_docs/074-query-audit-logging.md",
"title": "Query Audit Logging",
"url": "/docs/query-audit-logging/"
@@ -6024,6 +6156,23 @@
"title": "Reserved Keywords",
"url": "/docs/reserved-keywords/"
},
+ "Review the Java Stack Trace": {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "",
+ "next_url": "",
+ "parent": "Log and Debug",
+ "previous_title": "Modify logback.xml",
+ "previous_url": "/docs/modify-logback-xml/",
+ "relative_path": "_docs/log-and-debug/004-review-the-java-stack-trace.md",
+ "title": "Review the Java Stack Trace",
+ "url": "/docs/review-the-java-stack-trace/"
+ },
"SELECT": {
"breadcrumbs": [
{
@@ -8931,7 +9080,7 @@
"title": "Using Drill Explorer on Windows",
"url": "/docs/using-drill-explorer-on-windows/"
},
- "Using JDBC": {
+ "Using JDBC with SQuirreL on Windows": {
"breadcrumbs": [
{
"title": "ODBC/JDBC Interfaces",
@@ -8944,9 +9093,9 @@
"parent": "ODBC/JDBC Interfaces",
"previous_title": "Interfaces Introduction",
"previous_url": "/docs/interfaces-introduction/",
- "relative_path": "_docs/odbc-jdbc-interfaces/020-using-jdbc.md",
- "title": "Using JDBC",
- "url": "/docs/using-jdbc/"
+ "relative_path": "_docs/odbc-jdbc-interfaces/020-using-jdbc-with-squirrel-on-windows.md",
+ "title": "Using JDBC with SQuirreL on Windows",
+ "url": "/docs/using-jdbc-with-squirrel-on-windows/"
},
"Using MicroStrategy Analytics with Apache Drill": {
"breadcrumbs": [
@@ -9145,8 +9294,8 @@
"next_title": "ODBC on Linux and Mac Introduction",
"next_url": "/docs/odbc-on-linux-and-mac-introduction/",
"parent": "ODBC/JDBC Interfaces",
- "previous_title": "Using JDBC",
- "previous_url": "/docs/using-jdbc/",
+ "previous_title": "Using JDBC with SQuirreL on Windows",
+ "previous_url": "/docs/using-jdbc-with-squirrel-on-windows/",
"relative_path": "_docs/odbc-jdbc-interfaces/030-using-odbc-on-linux-and-mac-os-x.md",
"title": "Using ODBC on Linux and Mac OS X",
"url": "/docs/using-odbc-on-linux-and-mac-os-x/"
@@ -10570,8 +10719,8 @@
}
],
"children": [],
- "next_title": "Using JDBC",
- "next_url": "/docs/using-jdbc/",
+ "next_title": "Using JDBC with SQuirreL on Windows",
+ "next_url": "/docs/using-jdbc-with-squirrel-on-windows/",
"parent": "ODBC/JDBC Interfaces",
"previous_title": "ODBC/JDBC Interfaces",
"previous_url": "/docs/odbc-jdbc-interfaces/",
@@ -10592,9 +10741,9 @@
"parent": "ODBC/JDBC Interfaces",
"previous_title": "Interfaces Introduction",
"previous_url": "/docs/interfaces-introduction/",
- "relative_path": "_docs/odbc-jdbc-interfaces/020-using-jdbc.md",
- "title": "Using JDBC",
- "url": "/docs/using-jdbc/"
+ "relative_path": "_docs/odbc-jdbc-interfaces/020-using-jdbc-with-squirrel-on-windows.md",
+ "title": "Using JDBC with SQuirreL on Windows",
+ "url": "/docs/using-jdbc-with-squirrel-on-windows/"
},
{
"breadcrumbs": [
@@ -10776,8 +10925,8 @@
"next_title": "ODBC on Linux and Mac Introduction",
"next_url": "/docs/odbc-on-linux-and-mac-introduction/",
"parent": "ODBC/JDBC Interfaces",
- "previous_title": "Using JDBC",
- "previous_url": "/docs/using-jdbc/",
+ "previous_title": "Using JDBC with SQuirreL on Windows",
+ "previous_url": "/docs/using-jdbc-with-squirrel-on-windows/",
"relative_path": "_docs/odbc-jdbc-interfaces/030-using-odbc-on-linux-and-mac-os-x.md",
"title": "Using ODBC on Linux and Mac OS X",
"url": "/docs/using-odbc-on-linux-and-mac-os-x/"
@@ -11393,8 +11542,8 @@
}
],
"children": [],
- "next_title": "Query Audit Logging",
- "next_url": "/docs/query-audit-logging/",
+ "next_title": "Log and Debug",
+ "next_url": "/docs/log-and-debug/",
"parent": "Performance Tuning",
"previous_title": "Performance Tuning",
"previous_url": "/docs/performance-tuning/",
@@ -11414,6 +11563,18 @@
},
{
"breadcrumbs": [],
+ "children": [],
+ "next_title": "Query Audit Logging",
+ "next_url": "/docs/query-audit-logging/",
+ "parent": "",
+ "previous_title": "Performance Tuning Introduction",
+ "previous_url": "/docs/performance-tuning-introduction/",
+ "relative_path": "_docs/073-log-and-debug.md",
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ },
+ {
+ "breadcrumbs": [],
"children": [
{
"breadcrumbs": [
@@ -11436,8 +11597,8 @@
"next_title": "Getting Query Information",
"next_url": "/docs/getting-query-information/",
"parent": "",
- "previous_title": "Performance Tuning Introduction",
- "previous_url": "/docs/performance-tuning-introduction/",
+ "previous_title": "Log and Debug",
+ "previous_url": "/docs/log-and-debug/",
"relative_path": "_docs/074-query-audit-logging.md",
"title": "Query Audit Logging",
"url": "/docs/query-audit-logging/"
@@ -13224,14 +13385,95 @@
{
"breadcrumbs": [],
"children": [],
- "next_title": "",
- "next_url": "",
+ "next_title": "Log and Debug",
+ "next_url": "/docs/log-and-debug/",
"parent": "",
"previous_title": "2014 Q1 Drill Report",
"previous_url": "/docs/2014-q1-drill-report/",
"relative_path": "_docs/170-bylaws.md",
"title": "Project Bylaws",
"url": "/docs/project-bylaws/"
+ },
+ {
+ "breadcrumbs": [],
+ "children": [
+ {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "Error Messages",
+ "next_url": "/docs/error-messages/",
+ "parent": "Log and Debug",
+ "previous_title": "Log and Debug",
+ "previous_url": "/docs/log-and-debug/",
+ "relative_path": "_docs/log-and-debug/001-log-and-debug-introduction.md",
+ "title": "Log and Debug Introduction",
+ "url": "/docs/log-and-debug-introduction/"
+ },
+ {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "Modify logback.xml",
+ "next_url": "/docs/modify-logback-xml/",
+ "parent": "Log and Debug",
+ "previous_title": "Log and Debug Introduction",
+ "previous_url": "/docs/log-and-debug-introduction/",
+ "relative_path": "_docs/log-and-debug/002-error-messages.md",
+ "title": "Error Messages",
+ "url": "/docs/error-messages/"
+ },
+ {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "Review the Java Stack Trace",
+ "next_url": "/docs/review-the-java-stack-trace/",
+ "parent": "Log and Debug",
+ "previous_title": "Error Messages",
+ "previous_url": "/docs/error-messages/",
+ "relative_path": "_docs/log-and-debug/003-modify-logback.xml.md",
+ "title": "Modify logback.xml",
+ "url": "/docs/modify-logback-xml/"
+ },
+ {
+ "breadcrumbs": [
+ {
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
+ }
+ ],
+ "children": [],
+ "next_title": "",
+ "next_url": "",
+ "parent": "Log and Debug",
+ "previous_title": "Modify logback.xml",
+ "previous_url": "/docs/modify-logback-xml/",
+ "relative_path": "_docs/log-and-debug/004-review-the-java-stack-trace.md",
+ "title": "Review the Java Stack Trace",
+ "url": "/docs/review-the-java-stack-trace/"
+ }
+ ],
+ "next_title": "Log and Debug Introduction",
+ "next_url": "/docs/log-and-debug-introduction/",
+ "parent": "",
+ "previous_title": "Project Bylaws",
+ "previous_url": "/docs/project-bylaws/",
+ "relative_path": "_docs/sql-reference/sql-functions/073-log-and-debug.md",
+ "title": "Log and Debug",
+ "url": "/docs/log-and-debug/"
}
]
}
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/drill/blob/134b6ff8/_docs/073-log-and-debug.md
----------------------------------------------------------------------
diff --git a/_docs/073-log-and-debug.md b/_docs/073-log-and-debug.md
new file mode 100644
index 0000000..142d6b6
--- /dev/null
+++ b/_docs/073-log-and-debug.md
@@ -0,0 +1,3 @@
+---
+title: "Log and Debug"
+---
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/drill/blob/134b6ff8/_docs/log-and-debug/001-log-and-debug-introduction.md
----------------------------------------------------------------------
diff --git a/_docs/log-and-debug/001-log-and-debug-introduction.md b/_docs/log-and-debug/001-log-and-debug-introduction.md
new file mode 100644
index 0000000..473883f
--- /dev/null
+++ b/_docs/log-and-debug/001-log-and-debug-introduction.md
@@ -0,0 +1,15 @@
+---
+title: "Log and Debug Introduction"
+parent: "Log and Debug"
+---
+
+You can use the Drill logs in conjunction with query profiles to troubleshoot issues that you encounter. Drill uses Logback as its default logging system. Logback behavior is defined by configurations set in <drill_installation_directory>/conf/logback.xml.
+
+You can configure Logback to enable specific loggers for particular components. You can also enable Logback to output log messages to Lilith, a desktop application that you can use for socket logging. By default, Drill outputs log files to /var/log/drill.
+
+Drill provides two standard output files:
+
+* drillbit.out
+* drill.log
+
+Drill also provides a special file, drillbit_queries.json, on each Drill node. This log provides the QueryID and profile for every query run on a Drillbit. The Profile view in the Drill Web UI lists the last one-hundred queries that Drill ran. To see information for queries beyond the last one-hundred, you can view the drillbit_queries.json file on each Drill node.
http://git-wip-us.apache.org/repos/asf/drill/blob/134b6ff8/_docs/log-and-debug/002-error-messages.md
----------------------------------------------------------------------
diff --git a/_docs/log-and-debug/002-error-messages.md b/_docs/log-and-debug/002-error-messages.md
new file mode 100644
index 0000000..eb0c827
--- /dev/null
+++ b/_docs/log-and-debug/002-error-messages.md
@@ -0,0 +1,25 @@
+---
+title: "Error Messages"
+parent: "Log and Debug"
+---
+
+Drill produces several types of error messages. You can ignore issues that contain any of the following syntax:
+
+ * InterruptedException
+ * ChannelClosedException
+ * Connection reset by peer
+
+These issues typically result from a problem outside of the query process. However, if you encounter a java.lang.OutOfMemoryError error, take action and give Drill as much memory as possible to resolve the issue. See Configuring Drill Memory.
+
+Drill assigns an ErrorId to each error that occurs. An ErrorID is a unique identifier for a particular error that tells you which node assigned the error. For example,
+[ 1ee8e004-2fce-420f-9790-5c6f8b7cad46 on 10.1.1.109:31010 ]. You can log into the node that assigned the error and grep the Drill log for the ErrorId to get more information about the error.
+
+Thread names in the Drill logs also provide important information, including the query and fragment IDs. If a query fails, you can view the Java stack trace for the executing nodes to determine which part of the query is failing. An example thread, [42d7545c-c89b-47ab-9e38-2787bd200d4e:frag:1:173] includes QueryID 42d7545c-c89b-47ab-9e38-2787bd200d4e, MajorFragmentID 1, and MinorFragmentID 173.
+
+The following table provides descriptions for the IDs included in a thread:
+
+| ID Type | Description |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| QueryID | The identifier assigned to the query. You can locate a query in Drill Web UI by the QueryID and then cancel the query if needed. See Query Profiles for more information. |
+| MajorFragmentID | The identifier assigned to a major fragment. Major fragments map to the physical plan. You can see major fragment activity for a query in the Drill Web UI. See [Query Profiles]({{site.baseurl}}/docs/query-profiles) for more information. |
+| MinorFragmentID | The identifier assigned to the minor fragment. Minor fragments map to the parallelization of major fragments. See Query Profiles for more information. |
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/drill/blob/134b6ff8/_docs/log-and-debug/003-modify-logback.xml.md
----------------------------------------------------------------------
diff --git a/_docs/log-and-debug/003-modify-logback.xml.md b/_docs/log-and-debug/003-modify-logback.xml.md
new file mode 100644
index 0000000..ca506ad
--- /dev/null
+++ b/_docs/log-and-debug/003-modify-logback.xml.md
@@ -0,0 +1,54 @@
+---
+title: "Modify logback.xml"
+parent: "Log and Debug"
+---
+
+You can access logback.xml in ~<drill_installation_directory>/conf/. The default log level is set to INFO. You can enable debug logging and Lilith in logback.xml. Drill automatically picks up changes to logback.xml if you modify the file while Drill is running. You do not have to restart the cluster for Logback to pick up new settings.
+
+Logback.xml contains two appenders, STDOUT and FILE, that determine where Drill outputs logs. STDOUT output is directed to the console. FILE output is directed to drillbit.log and drillbit.out located in /var/log/drill/conf. You can modify these appenders to redirect log ouput to different locations.
+
+## Enable Debug Logging
+You can enable DEBUG on some loggers for additional information. Each of the classes listed below have a logger that you can add to logback.xml:
+
+* Task execution (similar to MR task submit output)
+ * org.apache.drill.exec.rpc.control.WorkEventBus
+ * org.apache.drill.exec.work.fragment.FragmentExecutor
+ * org.apache.drill.exec.work.foreman.QueryManager
+* Cluster cohesion and coordination
+ * org.apache.drill.exec.coord.zk.ZkClusterCoordinator
+* Query text and plans
+ * org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler
+
+To enable DEBUG on a logger, add the logger to logback.xml, and set the level value to “debug.”
+The following example shows a task execution logger that you can add to logback.xml:
+
+ <logger name="org.apache.drill.exec.work.foreman.QueryManager" additivity="false">
+ <level value="debug" />
+ <appender-ref ref="FILE" />
+ </logger>
+
+## Enable Lilith
+You can use Lilith and the socket appender for local debugging. Lillith connects to a Drillbit and shows logging as it happens.
+
+To enable log messages to output to Lilith, uncomment the following two sections in logback.xml and change LILITH_HOSTNAME to that of the machine running the Lilith application:
+
+ <appender name="SOCKET" class="de.huxhorn.lilith.logback.appender.ClassicMultiplexSocketAppender"> <Compressing>true</Compressing> <ReconnectionDelay>10000</ReconnectionDelay> <IncludeCallerData>true</IncludeCallerData> <RemoteHosts>${LILITH_HOSTNAME:-localhost}</RemoteHosts> </appender>
+
+ <logger name="org.apache.drill" additivity="false">
+ <level value="debug" />
+ <appender-ref ref="SOCKET" />
+ </logger>
+
+## Add the Hostname
+Logback includes a layout called PatternLayout that takes a logging event and returns a string. You can modify PatternLayout's conversion pattern to include the hostname in the log message. Add the hostname to the conversion pattern in logback.xml to identify which machine is sending log messages.
+
+The following example shows the conversion pattern with the hostname included:
+
+ <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
+ <encoder>
+ <pattern>$%d{HH:mm:ss.SSS} %property{HOSTNAME} [%thread] %-5level %logger{36} - %msg%n
+ </pattern>
+ </encoder>
+ </appender>
+
+
http://git-wip-us.apache.org/repos/asf/drill/blob/134b6ff8/_docs/log-and-debug/004-review-the-java-stack-trace.md
----------------------------------------------------------------------
diff --git a/_docs/log-and-debug/004-review-the-java-stack-trace.md b/_docs/log-and-debug/004-review-the-java-stack-trace.md
new file mode 100644
index 0000000..3b74397
--- /dev/null
+++ b/_docs/log-and-debug/004-review-the-java-stack-trace.md
@@ -0,0 +1,41 @@
+---
+title: "Review the Java Stack Trace"
+parent: "Log and Debug"
+---
+
+If a query is failing, you can use jstack to print the Java thread stack traces for the Drillbit process on the executing nodes to determine which part of the query is causing the failure. Drill labels threads based on query coordinates. For example, in the following thread you can see the QueryID, MajorFragementID, and MinorFragmentID, respectively:
+
+ "2ae226e1-f4c5-6253-e9ff-22ac1204935f:frag:3:2" daemon prio=10 tid=0x00007fa81167b800 nid=0x1431 waiting on condition [0x00007fa7aa3b3000]
+
+When you use jstack, grep for frag to see the fragments executing the query. To see the stack trace for a Drillbit process, you must have the Drillbit process ID. You can run jps to get the ID.
+
+## Use jstack to Review Stack Traces
+The following example shows you how to run jps to get the Drillbit process ID and grep for frag in the stack trace:
+
+ [root@drillats2 ~]# jps
+ 17455 jps
+ 1975 Drillbit
+ 31801 HRegionServer
+ 28858 TaskTracker
+ 22603 WardenMain
+
+In this example, the Drillbit process ID is 1975. Alternatively, you can grep for the Java processes running to identify the Drillbit process ID:
+
+ [root@drillats2 ~]# ps -el|grep java
+
+Once you have the Drillbit process ID, you can use jstack to view the stack trace of threads.
+
+ [root@drillats2 ~]# jstack 1975 | grep frag:
+ "2ae22585-bb7b-b482-0542-4ebd5225a249:frag:0:0" daemon prio=10 tid=0x00007fa782796800 nid=0x37a2 runnable [0x00007fa7866e4000]
+ "2ae225ab-c37a-31dc-227e-5f165e057f5f:frag:0:0" daemon prio=10 tid=0x00007fa7a004f000 nid=0x2946 runnable [0x00007fa7868e6000]
+ "2ae22598-2a77-5361-363b-291301fc44e8:frag:0:0" daemon prio=10 tid=0x00007fa782280800 nid=0x1bd4 runnable [0x00007fa7a4293000]
+ "2ae22582-c517-ec7a-8438-c81b7f5fdbce:frag:0:0" daemon prio=10 tid=0x0000000004651800 nid=0x144f runnable [0x00007fa7a53a4000]
+ "2ae226e1-8a2d-c079-a1d6-1f27c5a003bb:frag:13:2" daemon prio=10 tid=0x00007fa811ec3000 nid=0x143d waiting on condition [0x00007fa7a4799000]
+ "2ae226e1-8a2d-c079-a1d6-1f27c5a003bb:frag:9:2" daemon prio=10 tid=0x0000000004583800 nid=0x143c waiting on condition [0x00007fa7a4596000]
+ "2ae226e1-8a2d-c079-a1d6-1f27c5a003bb:frag:15:2" daemon prio=10 tid=0x00007fa81323f800 nid=0x1439 waiting on condition [0x00007fa7a4fa0000]
+ "2ae226e1-8a2d-c079-a1d6-1f27c5a003bb:frag:15:5" daemon prio=10 tid=0x0000000004582800 nid=0x1438 waiting on condition [0x00007fa7a4e9f000]
+ "2ae226e1-8a2d-c079-a1d6-1f27c5a003bb:frag:17:2" daemon prio=10 tid=0x00007fa813240800 nid=0x1435 waiting on condition [0x00007fa7a4496000]
+ "2ae226e1-f4c5-6253-e9ff-22ac1204935f:frag:3:2" daemon prio=10 tid=0x00007fa81167b800 nid=0x1431 waiting on condition [0x00007fa7aa3b3000]
+ "2ae226e1-f4c5-6253-e9ff-22ac1204935f:frag:2:2" daemon prio=10 tid=0x0000000004582000 nid=0x1430 waiting on condition [0x00007fa7a7bae000]
+ …
+
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/drill/blob/134b6ff8/_docs/odbc-jdbc-interfaces/020-using-jdbc-with-squirrel-on-windows.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/020-using-jdbc-with-squirrel-on-windows.md b/_docs/odbc-jdbc-interfaces/020-using-jdbc-with-squirrel-on-windows.md
new file mode 100755
index 0000000..be1b173
--- /dev/null
+++ b/_docs/odbc-jdbc-interfaces/020-using-jdbc-with-squirrel-on-windows.md
@@ -0,0 +1,164 @@
+---
+title: "Using JDBC with SQuirreL on Windows"
+parent: "ODBC/JDBC Interfaces"
+---
+To use the JDBC Driver to access Drill through SQuirreL, ensure that you meet the prerequisites and follow the steps in this section.
+### Prerequisites
+
+ * SQuirreL requires JRE 7
+ * Drill installed in distributed mode on one or multiple nodes in a cluster. Refer to the [Install Drill]({{ site.baseurl }}/docs/install-drill/) documentation for more information.
+ * The client must be able to resolve the actual hostname of the Drill node(s) with the IP(s). Verify that a DNS entry was created on the client machine for the Drill node(s).
+
+If a DNS entry does not exist, create the entry for the Drill node(s).
+
+ * For Windows, create the entry in the %WINDIR%\system32\drivers\etc\hosts file.
+ * For Linux and Mac, create the entry in /etc/hosts.
+<drill-machine-IP> <drill-machine-hostname>
+ Example: `127.0.1.1 maprdemo`
+
+----------
+
+### Step 1: Getting the Drill JDBC Driver
+
+The Drill JDBC Driver `JAR` file must exist in a directory on your Windows
+machine in order to configure the driver in the SQuirreL client.
+
+You can copy the Drill JDBC `JAR` file from the following Drill installation
+directory on the node with Drill installed, to a directory on your Windows
+machine:
+
+ <drill_installation_directory>/jars/jdbc-driver/drill-jdbc-all-<version>.jar
+
+Or, you can download the [apache-
+drill-0.9.0.tar.gz](http://apache.osuosl.org/drill/drill-0.9.0/apache-drill-0.9.0-src.tar.gz) file to a location on your Windows machine, and
+extract the contents of the file. You may need to use a decompression utility,
+such as [7-zip](http://www.7-zip.org/) to extract the archive. Once extracted,
+you can locate the driver in the following directory:
+
+ <windows_directory>\apache-drill-<version>\jars\jdbc-driver\drill-jdbc-all-<version>.jar
+
+----------
+
+### Step 2: Installing and Starting SQuirreL
+
+To install and start SQuirreL, complete the following steps:
+
+ 1. Download the SQuirreL JAR file for Windows from the following location:
+<http://www.squirrelsql.org/#installation>
+ 2. Double-click the SQuirreL `JAR` file. The SQuirreL installation wizard walks you through the installation process.
+ 3. When installation completes, navigate to the SQuirreL installation folder and then double-click `squirrel-sql.bat` to start SQuirreL.
+
+----------
+
+### Step 3: Adding the Drill JDBC Driver to SQuirreL
+
+To add the Drill JDBC Driver to SQuirreL, define the driver and create a
+database alias. The alias is a specific instance of the driver configuration.
+SQuirreL uses the driver definition and alias to connect to Drill so you can
+access data sources that you have registered with Drill.
+
+#### A. Define the Driver
+
+To define the Drill JDBC Driver, complete the following steps:
+
+1. In the SQuirreL toolbar, select **Drivers > New Driver**. The Add Driver dialog box appears.
+
+ 
+
+2. Enter the following information:
+
+ | Option | Description |
+ |------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Name | Name for the Drill JDBC Driver |
+ | Example URL | jdbc:drill:zk=<zookeeper_quorum>[;schema=<schema_to_use_as_default>]Example: jdbc:drill:zk=maprdemo:5181Note: The default ZooKeeper port is 2181. In a MapR cluster, the ZooKeeper port is 5181. |
+ | Website URL | jdbc:drill:zk=<zookeeper_quorum>[;schema=<schema_to_use_as_default>]Example: jdbc:drill:zk=maprdemo:5181Note: The default ZooKeeper port is 2181. In a MapR cluster, the ZooKeeper port is 5181. |
+ | Extra Class Path | Click Add and navigate to the JDBC JAR file location in the Windows directory:<windows_directory>/jars/jdbc-driver/drill-jdbc-all-0.6.0-incubating.jar Select the JAR file, click Open, and then click List Drivers. |
+ | Class Name | Select org.apache.drill.jdbc.Driver from the drop-down menu. |
+
+3. Click **OK**. The SQuirreL client displays a message stating that the driver registration is successful, and you can see the driver in the Drivers panel.
+
+ 
+
+#### B. Create an Alias
+
+To create an alias, complete the following steps:
+
+1. Select the **Aliases** tab.
+2. In the SQuirreL toolbar, select **Aliases >****New Alias**. The Add Alias dialog box appears.
+
+ 
+
+3. Enter the following information:
+
+ <table style='table-layout:fixed;width:100%'><tbody><tr>
+ <td valign="top" width="10%"><strong>Option</strong></td>
+ <td valign="top" style='width: 500px;'><strong>Description</strong></td>
+ </tr>
+ <tr>
+ <td valign="top">Alias Name</td>
+ <td valign="top">A unique name for the Drill JDBC Driver alias.</td>
+ </tr>
+ <tr>
+ <td valign="top">Driver</td>
+ <td valign="top">Select the Drill JDBC Driver.</td>
+ </tr>
+ <tr>
+ <td valign="top">URL</td>
+ <td valign="top">Enter the connection URL with the name of the Drill directory stored in ZooKeeper and the cluster ID:
+ <code>jdbc:drill:zk=<<em>zookeeper_quorum</em>>/<drill_directory_in_zookeeper>/<cluster_ID>;schema=<<em>schema_to_use_as_default</em>></code>
+ <em>The following examples show URLs for Drill installed on a single node:</em><br />
+ <span style="font-family: monospace;font-size: 14.0px;line-height: 1.4285715;background-color: transparent;">jdbc:drill:zk=10.10.100.56:5181/drill/demo_mapr_com-drillbits;schema=hive<br /></span>
+ <span style="font-family: monospace;font-size: 14.0px;line-height: 1.4285715;background-color: transparent;">jdbc:drill:zk=10.10.100.24:2181/drill/drillbits1;schema=hive<br /> </span>
+ <em>The following example shows a URL for Drill installed in distributed mode with a connection to a ZooKeeper quorum:</em>
+ <span style="font-family: monospace;font-size: 14.0px;line-height: 1.4285715;background-color: transparent;">jdbc:drill:zk=10.10.100.30:5181,10.10.100.31:5181,10.10.100.32:5181/drill/drillbits1;schema=hive</span>
+ <ul>
+ <li>Including a default schema is optional.</li>
+ <li>The ZooKeeper port is 2181. In a MapR cluster, the ZooKeeper port is 5181.</li>
+ <li>The Drill directory stored in ZooKeeper is <code>/drill</code>.</li>
+ <li>The Drill default cluster ID is<code> drillbits1</code>.</li>
+ </ul>
+ </td></tr><tr>
+ <td valign="top">User Name</td>
+ <td valign="top">admin</td>
+ </tr>
+ <tr>
+ <td valign="top">Password</td>
+ <td valign="top">admin</td>
+ </tr></tbody></table>
+4. Click **Ok**. The Connect to: dialog box appears.
+
+ 
+
+5. Click **Connect**. SQuirreL displays a message stating that the connection is successful.
+
+ 
+
+6. Click **OK**. SQuirreL displays a series of tabs.
+
+----------
+
+### Step 4: Running a Drill Query from SQuirreL
+
+Once you have SQuirreL successfully connected to your cluster through the
+Drill JDBC Driver, you can issue queries from the SQuirreL client. You can run
+a test query on some sample data included in the Drill installation to try out
+SQuirreL with Drill.
+
+To query sample data with Squirrel, complete the following steps:
+
+1. Click the SQL tab.
+2. Enter the following query in the query box:
+
+ SELECT * FROM cp.`employee.json`;
+
+ Example:
+ 
+
+3. Press **Ctrl+Enter** to run the query. The following query results display:
+
+ 
+
+You have successfully run a Drill query from the SQuirreL client.
+
+
+
http://git-wip-us.apache.org/repos/asf/drill/blob/134b6ff8/_docs/odbc-jdbc-interfaces/020-using-jdbc.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/020-using-jdbc.md b/_docs/odbc-jdbc-interfaces/020-using-jdbc.md
deleted file mode 100755
index d62a5a0..0000000
--- a/_docs/odbc-jdbc-interfaces/020-using-jdbc.md
+++ /dev/null
@@ -1,164 +0,0 @@
----
-title: "Using JDBC"
-parent: "ODBC/JDBC Interfaces"
----
-To use the JDBC Driver to access Drill through Squirrel, ensure that you meet the prerequisites and follow the steps in this section.
-### Prerequisites
-
- * SQuirreL requires JRE 7
- * Drill installed in distributed mode on one or multiple nodes in a cluster. Refer to the [Install Drill]({{ site.baseurl }}/docs/install-drill/) documentation for more information.
- * The client must be able to resolve the actual hostname of the Drill node(s) with the IP(s). Verify that a DNS entry was created on the client machine for the Drill node(s).
-
-If a DNS entry does not exist, create the entry for the Drill node(s).
-
- * For Windows, create the entry in the %WINDIR%\system32\drivers\etc\hosts file.
- * For Linux and Mac, create the entry in /etc/hosts.
-<drill-machine-IP> <drill-machine-hostname>
- Example: `127.0.1.1 maprdemo`
-
-----------
-
-### Step 1: Getting the Drill JDBC Driver
-
-The Drill JDBC Driver `JAR` file must exist in a directory on your Windows
-machine in order to configure the driver in the SQuirreL client.
-
-You can copy the Drill JDBC `JAR` file from the following Drill installation
-directory on the node with Drill installed, to a directory on your Windows
-machine:
-
- <drill_installation_directory>/jars/jdbc-driver/drill-jdbc-all-<version>.jar
-
-Or, you can download the [apache-
-drill-0.9.0.tar.gz](http://apache.osuosl.org/drill/drill-0.9.0/apache-drill-0.9.0-src.tar.gz) file to a location on your Windows machine, and
-extract the contents of the file. You may need to use a decompression utility,
-such as [7-zip](http://www.7-zip.org/) to extract the archive. Once extracted,
-you can locate the driver in the following directory:
-
- <windows_directory>\apache-drill-<version>\jars\jdbc-driver\drill-jdbc-all-<version>.jar
-
-----------
-
-### Step 2: Installing and Starting SQuirreL
-
-To install and start SQuirreL, complete the following steps:
-
- 1. Download the SQuirreL JAR file for Windows from the following location:
-<http://www.squirrelsql.org/#installation>
- 2. Double-click the SQuirreL `JAR` file. The SQuirreL installation wizard walks you through the installation process.
- 3. When installation completes, navigate to the SQuirreL installation folder and then double-click `squirrel-sql.bat` to start SQuirreL.
-
-----------
-
-### Step 3: Adding the Drill JDBC Driver to SQuirreL
-
-To add the Drill JDBC Driver to SQuirreL, define the driver and create a
-database alias. The alias is a specific instance of the driver configuration.
-SQuirreL uses the driver definition and alias to connect to Drill so you can
-access data sources that you have registered with Drill.
-
-#### A. Define the Driver
-
-To define the Drill JDBC Driver, complete the following steps:
-
-1. In the SQuirreL toolbar, select **Drivers > New Driver**. The Add Driver dialog box appears.
-
- 
-
-2. Enter the following information:
-
- | Option | Description |
- |------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
- | Name | Name for the Drill JDBC Driver |
- | Example URL | jdbc:drill:zk=<zookeeper_quorum>[;schema=<schema_to_use_as_default>]Example: jdbc:drill:zk=maprdemo:5181Note: The default ZooKeeper port is 2181. In a MapR cluster, the ZooKeeper port is 5181. |
- | Website URL | jdbc:drill:zk=<zookeeper_quorum>[;schema=<schema_to_use_as_default>]Example: jdbc:drill:zk=maprdemo:5181Note: The default ZooKeeper port is 2181. In a MapR cluster, the ZooKeeper port is 5181. |
- | Extra Class Path | Click Add and navigate to the JDBC JAR file location in the Windows directory:<windows_directory>/jars/jdbc-driver/drill-jdbc-all-0.6.0-incubating.jar Select the JAR file, click Open, and then click List Drivers. |
- | Class Name | Select org.apache.drill.jdbc.Driver from the drop-down menu. |
-
-3. Click **OK**. The SQuirreL client displays a message stating that the driver registration is successful, and you can see the driver in the Drivers panel.
-
- 
-
-#### B. Create an Alias
-
-To create an alias, complete the following steps:
-
-1. Select the **Aliases** tab.
-2. In the SQuirreL toolbar, select **Aliases >****New Alias**. The Add Alias dialog box appears.
-
- 
-
-3. Enter the following information:
-
- <table style='table-layout:fixed;width:100%'><tbody><tr>
- <td valign="top" width="10%"><strong>Option</strong></td>
- <td valign="top" style='width: 500px;'><strong>Description</strong></td>
- </tr>
- <tr>
- <td valign="top">Alias Name</td>
- <td valign="top">A unique name for the Drill JDBC Driver alias.</td>
- </tr>
- <tr>
- <td valign="top">Driver</td>
- <td valign="top">Select the Drill JDBC Driver.</td>
- </tr>
- <tr>
- <td valign="top">URL</td>
- <td valign="top">Enter the connection URL with the name of the Drill directory stored in ZooKeeper and the cluster ID:
- <code>jdbc:drill:zk=<<em>zookeeper_quorum</em>>/<drill_directory_in_zookeeper>/<cluster_ID>;schema=<<em>schema_to_use_as_default</em>></code>
- <em>The following examples show URLs for Drill installed on a single node:</em><br />
- <span style="font-family: monospace;font-size: 14.0px;line-height: 1.4285715;background-color: transparent;">jdbc:drill:zk=10.10.100.56:5181/drill/demo_mapr_com-drillbits;schema=hive<br /></span>
- <span style="font-family: monospace;font-size: 14.0px;line-height: 1.4285715;background-color: transparent;">jdbc:drill:zk=10.10.100.24:2181/drill/drillbits1;schema=hive<br /> </span>
- <em>The following example shows a URL for Drill installed in distributed mode with a connection to a ZooKeeper quorum:</em>
- <span style="font-family: monospace;font-size: 14.0px;line-height: 1.4285715;background-color: transparent;">jdbc:drill:zk=10.10.100.30:5181,10.10.100.31:5181,10.10.100.32:5181/drill/drillbits1;schema=hive</span>
- <ul>
- <li>Including a default schema is optional.</li>
- <li>The ZooKeeper port is 2181. In a MapR cluster, the ZooKeeper port is 5181.</li>
- <li>The Drill directory stored in ZooKeeper is <code>/drill</code>.</li>
- <li>The Drill default cluster ID is<code> drillbits1</code>.</li>
- </ul>
- </td></tr><tr>
- <td valign="top">User Name</td>
- <td valign="top">admin</td>
- </tr>
- <tr>
- <td valign="top">Password</td>
- <td valign="top">admin</td>
- </tr></tbody></table>
-4. Click **Ok**. The Connect to: dialog box appears.
-
- 
-
-5. Click **Connect**. SQuirreL displays a message stating that the connection is successful.
-
- 
-
-6. Click **OK**. SQuirreL displays a series of tabs.
-
-----------
-
-### Step 4: Running a Drill Query from SQuirreL
-
-Once you have SQuirreL successfully connected to your cluster through the
-Drill JDBC Driver, you can issue queries from the SQuirreL client. You can run
-a test query on some sample data included in the Drill installation to try out
-SQuirreL with Drill.
-
-To query sample data with Squirrel, complete the following steps:
-
-1. Click the SQL tab.
-2. Enter the following query in the query box:
-
- SELECT * FROM cp.`employee.json`;
-
- Example:
- 
-
-3. Press **Ctrl+Enter** to run the query. The following query results display:
-
- 
-
-You have successfully run a Drill query from the SQuirreL client.
-
-
-
http://git-wip-us.apache.org/repos/asf/drill/blob/134b6ff8/_docs/sql-reference/sql-functions/073-log-and-debug.md
----------------------------------------------------------------------
diff --git a/_docs/sql-reference/sql-functions/073-log-and-debug.md b/_docs/sql-reference/sql-functions/073-log-and-debug.md
new file mode 100644
index 0000000..142d6b6
--- /dev/null
+++ b/_docs/sql-reference/sql-functions/073-log-and-debug.md
@@ -0,0 +1,3 @@
+---
+title: "Log and Debug"
+---
\ No newline at end of file