[
https://issues.apache.org/jira/browse/SPARK-23189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337957#comment-16337957
]
Imran Rashid commented on SPARK-23189:
--------------------------------------
[~tgraves] -- why do you use the executors page instead of the stage page for
the active stage? Is it because you're typically running lots of jobs
simultaneously? Or is it just because its easier to navigate directly to the
executors page -- no need to have a jobid / stageId?
If its just having a convenient spot to navigate to, we could easily at a
"lastStage" / "lastJob" redirect, that would be pretty trivial. Or maybe there
is some other summary view we're missing to capture the current state of the
cluster -- the "executors" page may be close to what you want know but perhaps
we're actually missing something else.
I'm not trying to block this change or anything, just want to avoid UI clutter
and think a bit about the right way to add this.
> 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
