Skip to content

[SPARK-17526][Web UI]: Display the executor log links with the job failure message on Spark UI and Console - #15080

Closed
zhzhan wants to merge 2 commits into
apache:masterfrom
zhzhan:debug-log
Closed

[SPARK-17526][Web UI]: Display the executor log links with the job failure message on Spark UI and Console#15080
zhzhan wants to merge 2 commits into
apache:masterfrom
zhzhan:debug-log

Conversation

@zhzhan

Copy link
Copy Markdown
Contributor

What changes were proposed in this pull request?

Add the executor log links with the job failure message on Spark UI and Console

How was this patch tested?

The patch is manually tested.

In Console:

ERROR TaskSetManager: Task 0 in stage 0.0 failed 4 times; stdout: stdout_log_link stderr: stderr_log_link; aborting job ...

In WebUI

screen shot 2016-09-13 at 9 33 06 am

(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@zhzhanzhzhan changed the title SPARK-17526: add log links in job failuresSPARK-17526: Display the executor log links with the job failure message on Spark UI and ConsoleSep 13, 2016
@zhzhanzhzhan changed the title SPARK-17526: Display the executor log links with the job failure message on Spark UI and Console[SPARK-17526][Web UI]: Display the executor log links with the job failure message on Spark UI and ConsoleSep 13, 2016
@SparkQA

Copy link
Copy Markdown

Test build #65325 has finished for PR 15080 at commit 19fa189.

  • This patch fails MiMa tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
    • case class TaskSetFailed(taskSet: TaskSet, reason: String, exception: Option[Throwable],
    • case class WorkerOffer(executorId: String, host: String, cores: Int,

@SparkQA

Copy link
Copy Markdown

Test build #65332 has finished for PR 15080 at commit bcb7a2c.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@srowen

Copy link
Copy Markdown
Member

This is a lot of plumbing, to push info specific to a resource manager down a few levels. I don't think it's worth it just for a log message.

@zhzhan

Copy link
Copy Markdown
ContributorAuthor

@srowen Thanks for reviewing this. Any suggestion to improve it are welcomed. It does bother us a lot without being able to locate the debug log quickly in production.

@srowen

Copy link
Copy Markdown
Member

I would prefer not to make this change and close this PR.

srowen added a commit to srowen/spark that referenced this pull request Oct 12, 2016
@srowensrowen mentioned this pull request Oct 12, 2016
zifeif2 pushed a commit to zifeif2/spark that referenced this pull request Nov 22, 2025
Closesapache#15303Closesapache#15078Closesapache#15080Closesapache#15135Closesapache#14565Closesapache#12355Closesapache#15404
Author: Sean Owen <sowen@cloudera.com>
Closesapache#15451 from srowen/CloseStalePRs.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@zhzhan@SparkQA@srowen