[
https://issues.apache.org/jira/browse/DRILL-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395567#comment-16395567
]
ASF GitHub Bot commented on DRILL-6224:
---------------------------------------
Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/1160
I think I need to put up some tooltips.
We're getting the metrics from the `drill.allocator.root.[peak|used]`
values. I haven't seen a metric that shows the actual Direct allocation from
the system. What Drill seems to report is the current **actively** used Direct
memory. So, when running queries on the cluster, these numbers move up. The
percentage for Direct is the current usage as a percent of the peak memory that
was reported by the root allocator.
Check out any active Drillbit's `#metrics` page. The `drill.allocator.*`
entries are what I was referring to. JVM itself doesn't appear to expose the
Direct memory information readily.
> The metrics' page has gauges reset to near zero values and does not seem to
> update
> ----------------------------------------------------------------------------------
>
> Key: DRILL-6224
> URL: https://issues.apache.org/jira/browse/DRILL-6224
> Project: Apache Drill
> Issue Type: Bug
> Components: Web Server
> Affects Versions: 1.12.0
> Reporter: Kunal Khatua
> Priority: Major
>
> When viewing http://<hostname>:8047/metrics#gauges
> The gauges reset to near zero values and does not seem to update.
> Tracing the server calls made, I see the following:
> {code:json}
> {version: "3.0.0", gauges: {G1-Old-Generation.count: {value: 0},
> G1-Old-Generation.time: {value: 0},…},…}
> counters :
> {drill.connections.rpc.control.encrypted: {count: 0},…}
> gauges :
> {G1-Old-Generation.count: {value: 0}, G1-Old-Generation.time: {value: 0},…}
> histograms : {,…}
> meters : {}
> timers : {}
> version : "3.0.0"
> {code}
> This looks incorrect and would explain why the metrics appear to be
> incomplete.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
