[
https://issues.apache.org/jira/browse/IMPALA-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995312#comment-16995312
]
Sahil Takiar commented on IMPALA-9243:
--------------------------------------
We could even have a separate section on the /backends page that lists out the
blacklisted nodes, so the active and blacklisted nodes are in different tables.
Not advocating for a specific approach, just listing out ideas.
> Coordinator Web UI should list which executors have been blacklisted
> --------------------------------------------------------------------
>
> Key: IMPALA-9243
> URL: https://issues.apache.org/jira/browse/IMPALA-9243
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Sahil Takiar
> Priority: Major
>
> Currently, information about which nodes are blacklisted only shows up in
> runtime profiles and Coordinator logs. It would be nice to display
> blacklisting information in the Web UI as well so that a user can view which
> nodes are blacklisted at any given time.
> One potential place to put the blacklisting information is in the /backends
> page, which already lists out all the backends part of the cluster. A new
> column called "Status" which can have values of either "Active" or
> "Blacklisted" would be nice (perhaps we should re-factor the "Quiescing"
> column to use the new "Status" column as well). This is similar to what the
> Spark Web UI does for blacklisted nodes:
> [https://ndu0e1pobsf1dobtvj5nls3q-wpengine.netdna-ssl.com/wp-content/uploads/2019/08/BLACKLIST-SCHEDULING.png]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
