-
Notifications
You must be signed in to change notification settings - Fork 28.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-12339] [WebUI] Added a null check that was removed in SPARK-11206 #10405
Conversation
Looping in those involved with SPARK-11206: @carsonwang @JoshRosen @vanzin |
FYI the line in JobProgressListener.onTaskEnd that initializes the null value is 387. |
Test build #48089 has finished for PR 10405 at commit
|
Thanks for catching this. I think the null check here is necessary, and it seems the code that really pass a null taskMetrcis is from the |
Maybe a dumb question, but is it right that calling |
@srowen I thought the same thing so I looked into git history and git blame and found that this is how |
OK, merging into master, thanks. |
I'm seeing this issue been fixed in v2.0.0. Is there any possibility to fix this in v1.6.x ? |
@Naresh523 this particular issue doesn't appear to exist in 1.6 because the change that this fixes went into 2.0 |
I'm getting similar error logs [1]. there were no changes in application. |
Can this fix be added in 1.6 as well ? |
Updates made in SPARK-11206 missed an edge case which cause's a NullPointerException when a task is killed. In some cases when a task ends in failure taskMetrics is initialized as null (see JobProgressListener.onTaskEnd()). To address this a null check was added. Before the changes in SPARK-11206 this null check was called at the start of the updateTaskAccumulatorValues() function.