drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-6224) The metrics' page has gauges reset to near zero values and does not seem to update
Date Sun, 11 Mar 2018 23:31:00 GMT

    [ https://issues.apache.org/jira/browse/DRILL-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394700#comment-16394700
] 

ASF GitHub Bot commented on DRILL-6224:
---------------------------------------

GitHub user kkhatua opened a pull request:

    https://github.com/apache/drill/pull/1160

    DRILL-6224: Publish current memory usage for Drillbits in webpages

    The `metrics.ftl` page had gauges incorrectly set to near zero values. The commit for
metrics.ftl fixes that, and also provides an estimate of the current direct memory actively
in use (based on the `drill.allocator.root.used` value reported by the Drillbit)
    The `index.ftl` page expands this by additionally providing the active heap and direct
memory usage for all Drillbits. This is done by the JavaScript actively pinging all the Drillbits
on their current memory usage in 10 second intervals.
    The percentages in both cases indicate the % usage in terms of the max (heap) or the peak
(direct) observed.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kkhatua/drill DRILL-6224

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/1160.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1160
    
----
commit f098a2dc8644e9d3b11d032f6250c1f12f381f7e
Author: Kunal Khatua <kkhatua@...>
Date:   2018-03-10T08:04:35Z

    DRILL-6224: Publish current memory usage for Drillbits in webpages
    
    The `metrics.ftl` page had gauges incorrectly set to near zero values. The commit for
metrics.ftl fixes that, and also provides an estimate of the current direct memory actively
in use (based on the `drill.allocator.root.used` value reported by the Drillbit)
    The `index.ftl` page expands this by additionally providing the active heap and direct
memory usage for all Drillbits. This is done by the JavaScript actively pinging all the Drillbits
on their current memory usage in 10 second intervals.
    The percentages in both cases indicate the % usage in terms of the max (heap) or the peak
(direct) observed.

----


> 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)

Mime
View raw message