[
https://issues.apache.org/jira/browse/IMPALA-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032952#comment-17032952
]
ASF subversion and git services commented on IMPALA-9243:
---------------------------------------------------------
Commit 014f973e927a74b4d6020f756fe548e6a7b84ff5 in impala's branch
refs/heads/master from Thomas Tauber-Marshall
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=014f973 ]
IMPALA-9243: Add info about blacklisting decisions to the webui
This patch adds information about blacklisting decisions to the
/backends webui endpoint.
For the JSON, it adds an 'is_blacklisted' field to all backends, and
for and backends where 'is_blacklisted' is true it adds a
'blacklist_cause' field indicating the error status that led to the
backend getting blacklisted and an 'blacklist_time_remaining' field
indiciating how much longer the backend will remain on the blacklist.
It also adds counts for the number of blacklisted and quiescing
backends, if any, and the number of active (i.e. all other) backends.
For display, in order to prevent the table of backend information from
having too many columns (prior to this patch it already had 12), it
separates blacklisted, quiescing, and active backends into three
separate table, with the blacklisted and quiescing tables only getting
displayed if there are any such backends.
Additionally, tooltips are added next to the headers for the
blacklisted and quiescing tables that provide a brief explanation of
what it means for a backend to appear on there lists.
Using separate tables also facilitates having state-specific columns -
the blacklisted table displays columns for the blacklist cause and
time remaining. Future work could consider adding columns to the
quiescing table, such as time until the grace period and deadline
expires.
Testing:
- Manually ran various quiescing/blacklisting scenarios and confirmed
the /backends page displays as expected.
- Added cases to test_web_pages (to verify the new fields when nothing
is blacklisted) and test_blacklist.
Change-Id: Ia0c309315b142a50be102dcb516b36ec6cb3cf47
Reviewed-on: http://gerrit.cloudera.org:8080/15178
Reviewed-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> 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: Sub-task
> Reporter: Sahil Takiar
> Assignee: Thomas Tauber-Marshall
> Priority: Major
> Attachments: Screen Shot 2020-02-06 at 3.32.20 PM.png
>
>
> 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
