-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-8498][TUNGSTEN] fix npe in errorhandling path in unsafeshuffle writer #6918
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
Closed
holdenk
wants to merge
7
commits into
apache:master
from
holdenk:SPARK-8498-fix-npe-in-errorhandling-path-in-unsafeshuffle-writer
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
2e6abf7
Be more cautious when cleaning up during failed write and re-throw us…
holdenk ae0b7a7
Fix the test
holdenk e503b8c
Improve the test to ensure we aren't masking the underlying exception
holdenk 30e558d
go back to try/finally
holdenk 039d620
Add missing closeandwriteoutput
holdenk 855f9aa
Spelling - not my strongest suite. Fix Propegates to Propagates.
holdenk f807832
Log error if we can't throw it
holdenk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -139,6 +139,9 @@ public void write(Iterator<Product2<K, V>> records) throws IOException { | |
|
|
||
| @Override | ||
| public void write(scala.collection.Iterator<Product2<K, V>> records) throws IOException { | ||
| // Keep track of success so we know if we ecountered an exception | ||
| // We do this rather than a standard try/catch/re-throw to handle | ||
| // generic throwables. | ||
| boolean success = false; | ||
| try { | ||
| while (records.hasNext()) { | ||
|
|
@@ -147,8 +150,19 @@ public void write(scala.collection.Iterator<Product2<K, V>> records) throws IOEx | |
| closeAndWriteOutput(); | ||
| success = true; | ||
| } finally { | ||
| if (!success) { | ||
| sorter.cleanupAfterError(); | ||
| if (sorter != null) { | ||
| try { | ||
| sorter.cleanupAfterError(); | ||
| } catch (Exception e) { | ||
| // Only throw this error if we won't be masking another | ||
| // error. | ||
| if (success) { | ||
| throw e; | ||
| } else { | ||
| logger.error("In addition to a failure during writing, we failed during " + | ||
| "cleanup.", e); | ||
| } | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Shouldn't we log in the |
||
| } | ||
| } | ||
| } | ||
| } | ||
|
|
||
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could potentially use Utils.tryWithSafeFinally, which does this sort of annoying "try/catch in a try/catch" thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This class, along with a lot of the other Tungsten code, is written in Java, so we can't use
Utils.tryWithSafeFinallyhere.