From 6d618befe0fd960085122778e76cbb31fae2ba0b Mon Sep 17 00:00:00 2001 From: Bridget Bevens Date: Wed, 29 Jun 2016 10:53:27 -0700 Subject: [PATCH 1/2] update mailing list with note --- mailinglists.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/mailinglists.md b/mailinglists.md index b122aa5e7b8..4f2aa2a960c 100644 --- a/mailinglists.md +++ b/mailinglists.md @@ -13,5 +13,17 @@ All communication related to the Apache Drill project happens on the mailing lis * Subscribe: * Unsubscribe: * Post: - * [Archive](http://mail-archives.apache.org/mod_mbox/drill-dev/) + * [Archive](http://mail-archives.apache.org/mod_mbox/drill-dev/) + +**Note:** All contributions to the Apache projects are made by individual contributors, not organizations. Though companies may be paying their staff to commit code, promote the project, and so on, contributions are recognized on an individual basis. The ASF is vendor-neutral. + +When communicating through project channels, please follow these general guidelines: + +* Be courteous and respectful. +* Be concise in asking your question. Before doing so, try to read available documentation, FAQs, and mailing list history. +* Provide enough technical background to explain the issue. + +For additional guidelines, see [How To Ask Questions The Smart Way](http://www.catb.org/esr/faqs/smart-questions.html), and note the disclaimer: +*We are not a help desk for your project!* + From 4bb3aa839e16a50aa40d71ec8c39a010a1fc753d Mon Sep 17 00:00:00 2001 From: Bridget Bevens Date: Thu, 14 Jul 2016 11:41:09 -0700 Subject: [PATCH 2/2] update drill metrics wording this vs the --- .../070-monitoring-metrics.md | 84 +++++++++---------- 1 file changed, 42 insertions(+), 42 deletions(-) diff --git a/_docs/performance-tuning/070-monitoring-metrics.md b/_docs/performance-tuning/070-monitoring-metrics.md index 8d917502216..d53113bf7c5 100644 --- a/_docs/performance-tuning/070-monitoring-metrics.md +++ b/_docs/performance-tuning/070-monitoring-metrics.md @@ -1,42 +1,42 @@ ---- -title: "Monitoring Metrics" -date: -parent: "Performance Tuning" ---- - -As of Drill 1.7, Drill uses JMX ([Java Management Extensions](https://docs.oracle.com/javase/tutorial/jmx/)) to monitor queries at runtime. JMX provides the architecture to dynamically manage and monitor applications. JMX collects Drill system-level metrics that you can access through the Metrics tab in the Drill Web Console or a remote JMX monitoring tool, such as JConsole or the VisualVM + MBeans plugin. The Web Console Metrics tab contains the collected metrics as tables, counters, histograms, and gauges via JMX. - -## Remote Monitoring -You can enable the remote JMX Java feature to monitor a specific JVM from a remote location. You can enable remote JMX with or without authentication. See the [Java documentation](http://docs.oracle.com/javase/7/docs/technotes/guides/management/agent.html). - -In `$DRILL_HOME/conf/drill-env.sh`, use the `DRILLBIT_JAVA_OPTS` variable to pass the relevant parameters. For example, to add remote monitoring on port 8048 without authentication: - - export DRILLBIT_JAVA_OPTS=”$DRILLBIT_JAVA_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=8048” - -## Disabling Drill Metrics -JMX metric collection is enabled, by default. You can disable the metrics option if needed. - -In `$DRILL_HOME/conf/drill-env.sh`, set the `drill.metrics.jmx.enabled` option to false through the `DRILLBIT_JAVA_OPTS` variable. Add the variable in `drill-env.sh` if it does not exist: - - export DRILLBIT_JAVA_OPTS="$DRILLBIT_JAVA_OPTS -Ddrill.metrics.jmx.enabled=false" - -The following table lists the predefined Drill system-level metrics that you can view through a JMX monitoring tool or the Drill Web Console: - -| Metric | Description | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| drill.queries.running | The number of queries running for which the Drillbit is the Foreman. | -| drill.queries.completed | The number of queries completed, canceled, or failed for which the Drillbit was the Foreman. | -| drill.fragments.running | The number of query fragments currently running in the Drillbit. | -| drill.allocator.root.used | The amount of memory (in bytes) used by the internal memory allocator. | -| drill.allocator.root.peak | The peak amount of memory (in bytes) used by the internal memory allocator. | -| heap.used | The amount of heap memory (in bytes) used by the JVM. | -| non-heap.used | The amount of non-heap memory (in bytes) used by the JVM. | -| count | The number of live threads, including daemon and non-daemon threads. | -| fd.usage | The ratio of used file descriptors to total file descriptors on *nix systems. | -| direct.used | The amount of direct memory (in bytes) used by the JVM. This metric is useful for debugging Drill issues. | -| runnable.count | The number of threads executing an action in the JVM. This metric is useful for debugging Drill issues. | -| waiting.count | The number of threads waiting to execute. Typically, threads waiting on other threads to perform an action. This metric is useful for debugging Drill issues. | -| blocked.count | The number of threads that are blocked because they are waiting on a monitor lock. This metric is useful for debugging Drill issues. | - - - +--- +title: "Monitoring Metrics" +date: 2016-07-14 18:41:09 UTC +parent: "Performance Tuning" +--- + +As of Drill 1.7, Drill uses JMX ([Java Management Extensions](https://docs.oracle.com/javase/tutorial/jmx/)) to monitor queries at runtime. JMX provides the architecture to dynamically manage and monitor applications. JMX collects Drill system-level metrics that you can access through the Metrics tab in the Drill Web Console or a remote JMX monitoring tool, such as JConsole or the VisualVM + MBeans plugin. The Web Console Metrics tab contains the collected metrics as tables, counters, histograms, and gauges via JMX. + +## Remote Monitoring +You can enable the remote JMX Java feature to monitor a specific JVM from a remote location. You can enable remote JMX with or without authentication. See the [Java documentation](http://docs.oracle.com/javase/7/docs/technotes/guides/management/agent.html). + +In `$DRILL_HOME/conf/drill-env.sh`, use the `DRILLBIT_JAVA_OPTS` variable to pass the relevant parameters. For example, to add remote monitoring on port 8048 without authentication: + + export DRILLBIT_JAVA_OPTS=”$DRILLBIT_JAVA_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=8048” + +## Disabling Drill Metrics +JMX metric collection is enabled, by default. You can disable the metrics option if needed. + +In `$DRILL_HOME/conf/drill-env.sh`, set the `drill.metrics.jmx.enabled` option to false through the `DRILLBIT_JAVA_OPTS` variable. Add the variable in `drill-env.sh` if it does not exist: + + export DRILLBIT_JAVA_OPTS="$DRILLBIT_JAVA_OPTS -Ddrill.metrics.jmx.enabled=false" + +The following table lists the predefined Drill system-level metrics that you can view through a JMX monitoring tool or the Drill Web Console: + +| Metric | Description | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| drill.queries.running | The number of queries running for which this drillbit is the Foreman. | +| drill.queries.completed | The number of queries completed, canceled, or failed for which this drillbit was the Foreman. | +| drill.fragments.running | The number of query fragments currently running in the drillbit. | +| drill.allocator.root.used | The amount of memory (in bytes) used by the internal memory allocator. | +| drill.allocator.root.peak | The peak amount of memory (in bytes) used by the internal memory allocator. | +| heap.used | The amount of heap memory (in bytes) used by the JVM. | +| non-heap.used | The amount of non-heap memory (in bytes) used by the JVM. | +| count | The number of live threads, including daemon and non-daemon threads. | +| fd.usage | The ratio of used file descriptors to total file descriptors on *nix systems. | +| direct.used | The amount of direct memory (in bytes) used by the JVM. This metric is useful for debugging Drill issues. | +| runnable.count | The number of threads executing an action in the JVM. This metric is useful for debugging Drill issues. | +| waiting.count | The number of threads waiting to execute. Typically, threads waiting on other threads to perform an action. This metric is useful for debugging Drill issues. | +| blocked.count | The number of threads that are blocked because they are waiting on a monitor lock. This metric is useful for debugging Drill issues. | + + +