[
https://issues.apache.org/jira/browse/SPARK-23189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16338005#comment-16338005
]
Thomas Graves commented on SPARK-23189:
---------------------------------------
for large jobs the specific stage page is a pain to navigate. Most of the time
I go there i immediately shrink the executors table just to be able to see
task table more easily. All of those pages are a pain to navigate and find
things in my opinion, which is why we had a pr to change to datatables but got
back burnered based on vanzin request because changes in history server. that
is done now so I think could be done now but don't have time at the moment. But
that is just one reason.
Most of the time I can take a quick look at the job or stages tab (list of all
stages) to see what is happening at a high level, jump to executors tab to see
what is going there at a high level, and then only if needed load the specific
stages page. It might just be the way I use it. It also depends on what the
user is complaining about as to where I go first. I think if we fixed the
stage page to be more usable that might change. Like I already said I'm fine
with waiting on 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
