This is an automated email from the ASF dual-hosted git repository. bridgetb pushed a commit to branch gh-pages in repository https://gitbox.apache.org/repos/asf/drill.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new 88a5050 doc edit
88a5050 is described below
commit 88a5050d06d92b8c79b0a76445affddee0e0ef68
Author: Bridget Bevens <[email protected]>
AuthorDate: Fri Nov 9 20:28:28 2018 -0800
doc edit
---
_docs/performance-tuning/070-monitoring-metrics.md | 52 +++++++++++-----------
1 file changed, 25 insertions(+), 27 deletions(-)
diff --git a/_docs/performance-tuning/070-monitoring-metrics.md
b/_docs/performance-tuning/070-monitoring-metrics.md
index 5e2b374..bc52270 100644
--- a/_docs/performance-tuning/070-monitoring-metrics.md
+++ b/_docs/performance-tuning/070-monitoring-metrics.md
@@ -4,7 +4,7 @@ date: 2018-11-10
parent: "Performance Tuning"
---
-The Metrics page in the Drill Web UI
(http(s)://<drillbit-ip-address>:8047/metrics) lists JVM and operating system
metrics. You can use these metrics to debug the state of the cluster. The
Drill-specific metrics are prepended with `drill`, for example
`drill.fragments.running`. The other metrics relate specifically to the JVM.
+The Metrics page in the Drill Web UI
(`http(s)://<drillbit-ip-address>:8047/metrics`) lists JVM and operating system
metrics. You can use these metrics to debug the state of the cluster. The
Drill-specific metrics are prepended with `drill`, for example
`drill.fragments.running`. The other metrics relate specifically to the JVM.
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 see in the
Metrics tab in the Drill Web UI or a remote JMX monitoring tool, such as
JConsole or the VisualVM + MBeans plugin.
@@ -42,32 +42,30 @@ The following table lists the Drill-specific metrics in the
Gauges section of th
| Metric | Description
[...]
|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
-| 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.
[...]
-| 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.
[...]
-| drill.allocator.rpc.bit.control.peak | The maximum amount of bytes used
across all outgoing and incoming control connections for this Drillbit at
this moment.
[...]
-| drill.allocator.rpc.bit.control.used | The total number of bytes currently
used across all outgoing and incoming control connections for this Drillbit.
[...]
-| drill.allocator.rpc.bit.data.peak | The maximum amount of memory used
between all outgoing and incoming data connections for this Drillbit up to
this moment.
[...]
-| drill.allocator.rpc.bit.data.used | The total amount of memory used
between all outgoing and incoming data connections tor this Drillbit.
[...]
-| drill.allocator.rpc.bit.user.peak | The maximum amount of memory used
across all incoming Drill client connections to this Drillbit up to this
moment.
[...]
-| drill.allocator.rpc.bit.user.used | The total amount of memory used
across all incoming Drill client connections to this Drillbit.
[...]
-| drill.allocator.huge.size | Total size in bytes of huge (greater
than 16MB) direct buffers allocated until now
[...]
-| drill.allocator.huge.count | Number of allocations done for
direct buffer of size greater than 16MB. Each of these allocation happens
from OS which comes with an overhead rather from Netty's buffer pool.
[...]
-| drill.allocator.normal.count | Number of allocations done for
direct buffer of size less than equal to 16MB. Each of these allocation
happens from Netty's buffer pool. This counter is only updated in debug
environment when asserts are enabled to avoid overhead for each allocation
during normal execution.
[...]
-| drill.allocator.normal.size | Total size in bytes of normal (less
than and equal to 16MB) direct buffers allocated until now. This counter is
only updated in debug environment when asserts are enabled to avoid overhead
for each allocation during normal execution.
[...]
-| drill.allocator.normal.size | Total size in bytes of normal (less
than and equal to 16MB) direct buffers allocated until now. This counter is
only updated in debug environment when asserts are enabled to avoid overhead
for each allocation during normal execution.
[...]
-| 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.
[...]
-| 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.
[...]
-| load.avg | Returns the "recent cpu usage" for
the Drillbit process. This value is a double in the [0.0,1.0] interval. A
value of 0.0 means that none of the CPUs were running threads from the
Drillbit process during the recent period of time observed, while a value of
1.0 means that all CPUs were actively running threads from the Drillbit
process 100% of the time during the recent period being observed. Threads
from the Drillbit process includes t [...]
-| uptime | Total uptime of Drillbit JVM in
miliseconds. See
[getUptime()](https://docs.oracle.com/javase/7/docs/api/java/lang/management/RuntimeMXBean.html#getUptime()).
[...]
-
+| 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.
[...]
+| 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.
[...]
+| drill.allocator.rpc.bit.control.peak | The maximum amount of bytes used
across all outgoing and incoming control connections for this Drillbit at
this moment.
[...]
+| drill.allocator.rpc.bit.control.used | The total number of bytes currently
used across all outgoing and incoming control connections for this Drillbit.
[...]
+| drill.allocator.rpc.bit.data.peak | The maximum amount of memory used
between all outgoing and incoming data connections for this Drillbit up to
this moment.
[...]
+| drill.allocator.rpc.bit.data.used | The total amount of memory used
between all outgoing and incoming data connections tor this Drillbit.
[...]
+| drill.allocator.rpc.bit.user.peak | The maximum amount of memory used
across all incoming Drill client connections to this Drillbit up to this
moment.
[...]
+| drill.allocator.rpc.bit.user.used | The total amount of memory used
across all incoming Drill client connections to this Drillbit.
[...]
+| drill.allocator.huge.size | Total size in bytes of huge
(greater than 16MB) direct buffers allocated until now
[...]
+| drill.allocator.huge.count | Number of allocations done for direct
buffer of size greater than 16MB. Each of these allocation happens from OS
which comes with an overhead rather from Netty's buffer pool.
[...]
+| drill.allocator.normal.count | Number of allocations done for direct
buffer of size less than equal to 16MB. Each of these allocation happens from
Netty's buffer pool. This counter is only updated in debug environment when
asserts are enabled to avoid overhead for each allocation during normal
execution.
[...]
+| drill.allocator.normal.size | Total size in bytes of normal (less
than and equal to 16MB) direct buffers allocated until now. This counter is
only updated in debug environment when asserts are enabled to avoid overhead
for each allocation during normal execution.
[...]
+| drill.allocator.normal.size | Total size in bytes of normal (less
than and equal to 16MB) direct buffers allocated until now. This counter is
only updated in debug environment when asserts are enabled to avoid overhead
for each allocation during normal execution.
[...]
+| count | The number of live threads,
including daemon and non-daemon threads.
[...]
+| 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.
[...]
+| 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.
[...]
+| load.avg | Returns the "recent cpu usage" for
the Drillbit process. This value is a double in the [0.0,1.0] interval. A
value of 0.0 means that none of the CPUs were running threads from the
Drillbit process during the recent period of time observed, while a value of
1.0 means that all CPUs were actively running threads from the Drillbit
process 100% of the time during the recent period being observed. Threads
from the Drillbit process includes t [...]
+| uptime | Total uptime of Drillbit JVM in
miliseconds. See
[getUptime()](https://docs.oracle.com/javase/7/docs/api/java/lang/management/RuntimeMXBean.html#getUptime()).
[...]
## Counters
