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.

----


---

Reply via email to