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-6289) Cluster view should show more relevant information
Date Mon, 09 Apr 2018 18:25:00 GMT

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

ASF GitHub Bot commented on DRILL-6289:

Github user kkhatua commented on the issue:

    @arina-ielchiieva You're correct about the inability to shutdown other Drillbits from
the WebUI. But, from what @dvjyothsna explained, it seems that this was the result of a technical
hurdle with HTTP**S** protocol. My understanding was that issuing shutdown to secure remote
nodes won't work because of lack of certificates for those nodes, making it difficult for
the remote Drillbit to authenticate the shutdown command. Keeping that in mind, the SHUTDOWN
buttons would appear only for unsecured  Drillbits, i.e. when Authentication is **_not_**
    For setups requiring Authentication, the shutdown button would not appear.

> 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

View raw message