[
https://issues.apache.org/jira/browse/DRILL-6364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457251#comment-16457251
]
ASF GitHub Bot commented on DRILL-6364:
---------------------------------------
Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/1241
Screenshot of when UI node `kk127` goes down. The UI's javascript logic
queries other Drillbits in the list (in this case, `kk128`) and discovers two
new previously unseen Drillbits - `kk130` and `kk129`, discovered in the
sequence in which they were discovered in the cluster. State changes are marked
correctly, with shutdown buttons disabled.
A prompt in the form of an orange refresh button near the Drillbit count
indicates the need to refresh. Alternatively, one of the other nodes can be
used for pop-out of a new WebUI.
> WebUI does not cleanly handle shutdown and state toggling when Drillbits go
> on and offline
> ------------------------------------------------------------------------------------------
>
> Key: DRILL-6364
> URL: https://issues.apache.org/jira/browse/DRILL-6364
> Project: Apache Drill
> Issue Type: Bug
> Components: Web Server
> Reporter: Kunal Khatua
> Assignee: Kunal Khatua
> Priority: Major
> Fix For: 1.14.0
>
>
> When the webpage is loaded the first time, the shutdown button is enabled by
> default, which might not be correct, since scenarios like HTTPS, etc does not
> support this for remote bits. (i.e the user needs to navigate to that node's
> UI for shutting it down).
> Similarly, when a previously unseen Drillbit comes online, the node will not
> be rendered until the page is refreshed by the user.
> Lastly, if the node from whom the UI page was served goes down, the status
> update for the rest of the cluster is not updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
