ASF GitHub Bot commented on DRILL-6289:

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

    --- Diff: exec/java-exec/src/main/resources/rest/index.ftl ---
    @@ -52,12 +52,18 @@
    -              <th>Address</th>
    +              <th title="Drillbits in Cluster" style="cursor: 
help;">Address <span class="glyphicon glyphicon-info-sign" 
    +              <th title="Heap Memory in use (as percent of Total Heap)" 
style="cursor: help;">Heap Memory Usage <span class="glyphicon 
glyphicon-info-sign" style="font-size:100%"/></th>
    +              <th title="Direct Memory ACTIVELY in use (as percent of Peak 
Usage so far).&#013;The percentage is an estimate of the total because the 
Netty library directly negotiates with the OS for memory" style="cursor: 
help;">Direct Memory Usage <span class="glyphicon glyphicon-info-sign" 
    --- End diff --
    1. The problem is that the Peak Usage can go up over time. Adding 'so far' 
indicates that this isn't a final value.
    2. We could drop it, but this was meant to indicate less confusion for 
users wondering why the MaxDirectMemory value is not reflected here. It does. 
however, make it rather verbose.

> Cluster view should show more relevant information
> --------------------------------------------------
>                 Key: DRILL-6289
>                 URL: https://issues.apache.org/jira/browse/DRILL-6289
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Web Server
>    Affects Versions: 1.13.0
>            Reporter: Kunal Khatua
>            Assignee: Kunal Khatua
>            Priority: Major
>             Fix For: 1.14.0
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> When fixing DRILL-6224, I noticed that the same information can be very 
> useful to have in the cluster view shown on a Drillbit's homepage. 
> The proposal is to show the following:
> # Heap Memory in use
> # Direct Memory (actively) in use - Since we're not able to get the total 
> memory held by Netty at the moment, but only what is currently allocated to 
> running queries
> # Process CPU
> # Average (System) Load Factor 
> Information such as the port numbers don't help much during general cluster 
> health, so it might be worth removing this information if more real-estate is 
> needed.

This message was sent by Atlassian JIRA

Reply via email to