[
https://issues.apache.org/jira/browse/SPARK-23189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335888#comment-16335888
]
Imran Rashid commented on SPARK-23189:
--------------------------------------
yeah I think just active stages might be fine. In general, that will not be a
long list (though of course, it could be long ...).
honestly, I am trying to understand exactly what this will be used for. If you
just want to know which executors / nodes might be bad, looking at "failed
tasks" is probably better. If its to see what is going on an active stage, it
seems like you'd look at the stage page for that particular stage instead (as
attila is handling in SPARK-22577).
The other use I could think of is finding "repeat offenders", if there are some
executors which keep getting put on the taskset blacklist, but for some reason
don't get put on the application blacklist (eg, wrong thresholds). But for
that, you'd want to see the blacklisting for stages even after they had
completed.
> 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
