[ 
https://issues.apache.org/jira/browse/SPARK-23189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335769#comment-16335769
 ] 

Attila Zsolt Piros commented on SPARK-23189:
--------------------------------------------

In case of listing only the active stages only I have only one performance 
concern / question. It is easy to store the blacklisted stageId-s for a live 
executor during blacklisting. But n case of stage completion without 
introducing an extra map from stage ID to executor ID I can only find the 
relevant executors with a complete search.

Moreover I have an idea: what about showing just the last 3 by default but 
having a tooltip containing all the stages in case of hovering above the item? 
[~ajbozarth] is using a tooltip an option on the UI? I have seen some in the 
event timeline, but within a table I have found none.

> reflect stage level blacklisting on executor tab 
> -------------------------------------------------
>
>                 Key: SPARK-23189
>                 URL: https://issues.apache.org/jira/browse/SPARK-23189
>             Project: Spark
>          Issue Type: Bug
>          Components: Web UI
>    Affects Versions: 2.1.1
>            Reporter: Attila Zsolt Piros
>            Priority: Major
>
> This issue is the came during working on SPARK-22577 where the conclusion was 
> not only stage tab should reflect stage and application level backlisting but 
> also the executor tab should be extended with stage level backlisting 
> information.
> As [~irashid] and [~tgraves] are discussed the backlisted stages should be 
> listed for an executor like "*stage[ , ,...]*". One idea was to list only the 
> most recent 3 of the blacklisted stages another was list all the active 
> stages which are blacklisted.  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to