Uh oh!
There was an error while loading. Please reload this page.
[SPARK-20250][Core]Improper OOM error when a task been killed while spilling data - #18090
Closed
ConeyLiu wants to merge 1 commit into
Closed
[SPARK-20250][Core]Improper OOM error when a task been killed while spilling data#18090ConeyLiu wants to merge 1 commit into
ConeyLiu wants to merge 1 commit into
Conversation
…ed while spilling data
ConeyLiu
commented
May 25, 2017
ContributorAuthor
Hi @cloud-fan, @srowen, Can you help take a look ? Thanks a lot. |
cloud-fan
commented
May 25, 2017
Contributor
ok to test |
| break; | ||
| } | ||
| } | ||
| } catch (ClosedByInterruptException e) { |
Contributor
There was a problem hiding this comment.
surprisingly this is also IOException... good catch!
cloud-fan
commented
May 25, 2017
Contributor
LGTM |
1 similar comment
viirya
commented
May 25, 2017
Member
LGTM |
SparkQA
commented
May 25, 2017
Test build #77329 has finished for PR 18090 at commit
|
asfgit pushed a commit
that referenced
this pull request
May 25, 2017
…spilling data ## What changes were proposed in this pull request? Currently, when a task is calling spill() but it receives a killing request from driver (e.g., speculative task), the `TaskMemoryManager` will throw an `OOM` exception. And we don't catch `Fatal` exception when a error caused by `Thread.interrupt`. So for `ClosedByInterruptException`, we should throw `RuntimeException` instead of `OutOfMemoryError`. https://issues.apache.org/jira/browse/SPARK-20250?jql=project%20%3D%20SPARK ## How was this patch tested? Existing unit tests. Author: Xianyang Liu <xianyang.liu@intel.com> Closes#18090 from ConeyLiu/SPARK-20250. (cherry picked from commit 731462a) Signed-off-by: Wenchen Fan <wenchen@databricks.com>
asfgit pushed a commit
that referenced
this pull request
May 25, 2017
…spilling data Currently, when a task is calling spill() but it receives a killing request from driver (e.g., speculative task), the `TaskMemoryManager` will throw an `OOM` exception. And we don't catch `Fatal` exception when a error caused by `Thread.interrupt`. So for `ClosedByInterruptException`, we should throw `RuntimeException` instead of `OutOfMemoryError`. https://issues.apache.org/jira/browse/SPARK-20250?jql=project%20%3D%20SPARK Existing unit tests. Author: Xianyang Liu <xianyang.liu@intel.com> Closes#18090 from ConeyLiu/SPARK-20250. (cherry picked from commit 731462a) Signed-off-by: Wenchen Fan <wenchen@databricks.com>
asfgit pushed a commit
that referenced
this pull request
May 25, 2017
…spilling data Currently, when a task is calling spill() but it receives a killing request from driver (e.g., speculative task), the `TaskMemoryManager` will throw an `OOM` exception. And we don't catch `Fatal` exception when a error caused by `Thread.interrupt`. So for `ClosedByInterruptException`, we should throw `RuntimeException` instead of `OutOfMemoryError`. https://issues.apache.org/jira/browse/SPARK-20250?jql=project%20%3D%20SPARK Existing unit tests. Author: Xianyang Liu <xianyang.liu@intel.com> Closes#18090 from ConeyLiu/SPARK-20250. (cherry picked from commit 731462a) Signed-off-by: Wenchen Fan <wenchen@databricks.com>
cloud-fan
commented
May 25, 2017
Contributor
thanks, merging to master/2.2/2.1/2.0! |
ContributorAuthor
thanks @cloud-fan@viirya for reviewing. |
jzhuge pushed a commit
to jzhuge/spark
that referenced
this pull request
Aug 20, 2018
…spilling data Currently, when a task is calling spill() but it receives a killing request from driver (e.g., speculative task), the `TaskMemoryManager` will throw an `OOM` exception. And we don't catch `Fatal` exception when a error caused by `Thread.interrupt`. So for `ClosedByInterruptException`, we should throw `RuntimeException` instead of `OutOfMemoryError`. https://issues.apache.org/jira/browse/SPARK-20250?jql=project%20%3D%20SPARK Existing unit tests. Author: Xianyang Liu <xianyang.liu@intel.com> Closesapache#18090 from ConeyLiu/SPARK-20250. (cherry picked from commit 731462a) Signed-off-by: Wenchen Fan <wenchen@databricks.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Currently, when a task is calling spill() but it receives a killing request from driver (e.g., speculative task), the
TaskMemoryManagerwill throw anOOMexception. And we don't catchFatalexception when a error caused byThread.interrupt. So forClosedByInterruptException, we should throwRuntimeExceptioninstead ofOutOfMemoryError.https://issues.apache.org/jira/browse/SPARK-20250?jql=project%20%3D%20SPARK
How was this patch tested?
Existing unit tests.