Skip to content

Conversation

@gerashegalov
Copy link
Contributor

What changes were proposed in this pull request?

Include stacktrace in the diagnostics message upon abnormal unregister from RM

How was this patch tested?

Tested with a failing job, and confirmed a stacktrace in the client output and YARN webUI.

@srowen
Copy link
Member

srowen commented Feb 1, 2018

That seems reasonably harmless; CC @vanzin

@vanzin
Copy link
Contributor

vanzin commented Feb 1, 2018

ok to test

@SparkQA
Copy link

SparkQA commented Feb 1, 2018

Test build #86945 has finished for PR 20470 at commit b962167.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
  • \"User class threw exception: \" + StringUtils.stringifyException(cause))

@vanzin
Copy link
Contributor

vanzin commented Feb 1, 2018

Merging to master / 2.3.

asfgit pushed a commit that referenced this pull request Feb 1, 2018
## What changes were proposed in this pull request?

Include stacktrace in the diagnostics message upon abnormal unregister from RM

## How was this patch tested?
Tested with a failing job, and confirmed a stacktrace in the client output and YARN webUI.

Author: Gera Shegalov <gera@apache.org>

Closes #20470 from gerashegalov/gera/stacktrace-diagnostics.

(cherry picked from commit 032c11b)
Signed-off-by: Marcelo Vanzin <vanzin@cloudera.com>
@asfgit asfgit closed this in 032c11b Feb 1, 2018
@gerashegalov gerashegalov deleted the gera/stacktrace-diagnostics branch February 2, 2018 00:01
Sign up for free to 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.

4 participants