[ https://issues.apache.org/jira/browse/DRILL-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439797#comment-16439797
]
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_r181834064
--- Diff: exec/java-exec/src/main/resources/rest/index.ftl ---
@@ -283,20 +308,114 @@
alert(errorThrown);
},
success: function(data) {
- alert(data["response"]);
+ alert(data["response"]);
button.prop('disabled',true).css('opacity',0.5);
}
});
}
}
- </#if>
+
+ function remoteShutdown(button,host) {
+ var url = location.protocol + "//" + host + "/gracefulShutdown";
+ var result = $.ajax({
+ type: 'POST',
+ url: url,
+ contentType : 'text/plain',
+ complete: function(data) {
+ alert(data.responseJSON["response"]);
+ button.prop('disabled',true).css('opacity',0.5);
+ }
+ });
+ }
+ </#if>
+
+ function popOutRemoteDbitUI(dbitHost, dbitPort) {
--- End diff --
We can't put this and the remaining functions within the IF block since the localhost
operations are still valid. i.e. an authenticated client on a specific Drillbit can ping that
Drillbit for refresh of the metrics. Only shutdown function needs to be managed with the IF
block
> 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)
|