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

Imran Rashid commented on SPARK-23189:
--------------------------------------

OK, since nobody feels strongly and to avoid bike-shedding here, my suggestion 
to move forward is Attila goes ahead with this since it should be a small 
change, but if it complicated for whatever reason its probably not worth 
sinking a lot of time into.

I'd rather we just fixed the stage page to be better -- I don't like adding 
this if we plan on ripping it out later.  But also realize we don't have a ton 
of contributors working on the UI now, so who knows when the other UI stuff 
will happen, so we can make this small change, since I think you probably have 
a pretty good sense of what would be useful in these pages.


> 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