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

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

Github user kkhatua commented on the issue:

    https://github.com/apache/drill/pull/1160
  
    During a freshly setup Drillbit:
    
![image](https://user-images.githubusercontent.com/4335237/37847547-644fa67c-2e8e-11e8-9aa7-2b4adf499cd0.png)
    
    While running 2 large (600M rows) join query on a 4 node setup, and one 
completes:
    
![image](https://user-images.githubusercontent.com/4335237/37847633-b4dd5a76-2e8e-11e8-9c1d-87c3a0f9f3e7.png)
    
    The Heap Usage percentage is based on {{heapUsed/heapMax}}
    The Actively Used Direct percentage is based on 
{{currentDirectInUse/PeakDirectUsed}} 
    This is because the actual total direct memory used by Netty is not 
exposed. However, this does tell how much the Drillbit is using at the moment.


> 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
>            Assignee: Kunal Khatua
>            Priority: Major
>              Labels: ready-to-commit
>             Fix For: 1.14.0
>
>
> 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)

Reply via email to