[
https://issues.apache.org/jira/browse/DRILL-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442864#comment-16442864
]
ASF GitHub Bot commented on DRILL-6289:
---------------------------------------
Github user kkhatua commented on a diff in the pull request:
https://github.com/apache/drill/pull/1203#discussion_r182500652
--- Diff: exec/java-exec/src/main/resources/rest/index.ftl ---
@@ -67,9 +73,15 @@
<td>${i}</td>
<td id="address" >${drillbit.getAddress()}<#if
drillbit.isCurrent()>
<span class="label label-info"
id="current">Current</span>
+ <#else>
+ <a
onclick="popOutRemoteDbitUI('${drillbit.getAddress()}','${drillbit.getHttpPort()}');"
style="cursor:pointer;color:blue" title="Open in new window"><span
class="glyphicon glyphicon-new-window"/></a>
--- End diff --
The `shutdown()` method should be in the freemarker's IF block that checks
for authentication. Any other method is benign and does not risk changing the
state of the Drillbit.
Also, this method simply will pop out a new window from which that
Drillbit's UI can be accessed. This should help if someone wishes to navigate
to that node to, say, review logs or even submit queries with that node as the
foreman, without having to type the address (which might have a different HTTP
port).
> 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
(v7.6.3#76005)