-
Notifications
You must be signed in to change notification settings - Fork 440
TEZ-4334: Fix deadlock in ShuffleScheduler between ShuffleScheduler.close() and the ShufflePenaltyReferee thread #273
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
Merged
Conversation
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
This comment was marked as outdated.
This comment was marked as outdated.
6a679e4 to
f9630d7
Compare
This comment was marked as outdated.
This comment was marked as outdated.
…lose() and the ShufflePenaltyReferee thread
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
Contributor
|
Good catch. This should happen more in clusters with bad nodes (in exception codepath). LGTM. +1 |
zhuxt2015
pushed a commit
to zhuxt2015/tez
that referenced
this pull request
May 14, 2024
…lose() and the ShufflePenaltyReferee thread (apache#273) (Laszlo Bodor, Sungwoo Park, reviewed by Rajesh Balamohan) (cherry picked from commit 25a9536)
prabhjyotsingh
pushed a commit
to acceldata-io/tez
that referenced
this pull request
Nov 11, 2024
…lose() and the ShufflePenaltyReferee thread (apache#273) (Laszlo Bodor, Sungwoo Park, reviewed by Rajesh Balamohan) (cherry picked from commit 25a9536)
prabhjyotsingh
pushed a commit
to acceldata-io/tez
that referenced
this pull request
Nov 20, 2024
…lose() and the ShufflePenaltyReferee thread (apache#273) (Laszlo Bodor, Sungwoo Park, reviewed by Rajesh Balamohan) (cherry picked from commit 25a9536) (cherry picked from commit 6b5355a)
prabhjyotsingh
added a commit
to acceldata-io/tez
that referenced
this pull request
Nov 20, 2024
…cheduler.close() and the ShufflePenaltyReferee thread (apache#273) (Laszlo Bodor, Sungwoo Park, reviewed by Rajesh Balamohan) (#17) (cherry picked from commit 25a9536) (cherry picked from commit 6b5355a) Co-authored-by: Bodor Laszlo <[email protected]>
shubhluck
pushed a commit
to acceldata-io/tez
that referenced
this pull request
Nov 21, 2024
…cheduler.close() and the ShufflePenaltyReferee thread (apache#273) (Laszlo Bodor, Sungwoo Park, reviewed by Rajesh Balamohan) (#17) (cherry picked from commit 25a9536) (cherry picked from commit 6b5355a) Co-authored-by: Bodor Laszlo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This patch resolved a deadlock between different parts of ShuffleSheduler:
tez/tez-runtime-library/src/main/java/org/apache/tez/runtime/library/common/shuffle/orderedgrouped/ShuffleScheduler.java
Line 1062 in 6bd6f9c
tez/tez-runtime-library/src/main/java/org/apache/tez/runtime/library/common/shuffle/orderedgrouped/ShuffleScheduler.java
Line 1336 in 6bd6f9c
The patch
a) removed synchronized keyword from copyFailed method, but let parts of that method remain sync
b) removed the boolean return mess from methods that called from copyFailed and introduced a clearer IOException pattern and let the exceptionReporter be called from a non-sync part, at one single place