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

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

I have introduced a new attribute for live executors called blacklistedInStages.

It is a set containing the StageIDs where the executor was blacklisted.

So on the UI the label can be one of the followings:
- "Blacklisted" when the executor is blacklisted application level (old flag)
- "Dead" when the executor is not Blacklisted and not Active
- "Blacklisted in Stages: [...]" when the executor is Active but the 
blacklistedInStages set is not empty  
- "Active" when the executor is Active and blacklistedInStages set is empty

> 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
>         Attachments: afterStageCompleted.png, backlisted.png, 
> multiple_stages.png
>
>
> 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