drill-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bridg...@apache.org
Subject drill git commit: edit per MD-679 to modify logback.xml
Date Tue, 09 Feb 2016 21:36:11 GMT
Repository: drill
Updated Branches:
  refs/heads/gh-pages 9937f9512 -> 7414e6c68


edit per MD-679 to modify logback.xml


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

Branch: refs/heads/gh-pages
Commit: 7414e6c687bf2157977dbdae6aacf2cd7d9799ed
Parents: 9937f95
Author: Bridget Bevens <bbevens@maprtech.com>
Authored: Tue Feb 9 13:33:57 2016 -0800
Committer: Bridget Bevens <bbevens@maprtech.com>
Committed: Tue Feb 9 13:33:57 2016 -0800

----------------------------------------------------------------------
 _docs/log-and-debug/003-modify-logback.xml.md | 110 ++++++++++-----------
 1 file changed, 55 insertions(+), 55 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/7414e6c6/_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
index ac01f6d..924c8bd 100644
--- a/_docs/log-and-debug/003-modify-logback.xml.md
+++ b/_docs/log-and-debug/003-modify-logback.xml.md
@@ -1,55 +1,55 @@
----
-title: "Modify logback.xml"
-date:  
-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>
-
-
+---
+title: "Modify logback.xml"
+date: 2016-02-09 21:33:59 UTC
+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
should automatically pick up changes to `logback.xml` if you modify the file while Drill is
running. If not, 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>
+
+


Mime
View raw message