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

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

Github user kkhatua commented on a diff in the pull request:

    https://github.com/apache/drill/pull/1160#discussion_r176592068
  
    --- Diff: exec/java-exec/src/main/resources/rest/index.ftl ---
    @@ -192,6 +199,8 @@
           var port = getPortNum();
           var timeout;
           var size = $("#size").html();
    +      reloadMemory();
    +      setInterval(reloadMemory, refreshTime);
    --- End diff --
    
    That's because the scheduler for graceful shutdown can change, while in 
this case we need a periodic refresh that shouldn't change.
    As for a Drillbit going down, it can always come back online. As long as 
the page continues to list the Drillbit and it does get updated to reflect the 
status as "ONLINE" again, we should be pinging for the metrics too.


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