-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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-25286][CORE] Removing the dangerous parmap #22292
Conversation
This reverts commit 72cdfeb.
@zsxwing @gatorsmile Please, have a look at the PR. |
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.
LGTM except one nit
@@ -315,7 +315,9 @@ private[streaming] object FileBasedWriteAheadLog { | |||
implicit val ec = executionContext |
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.
nit: this line is not needed
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.
LGTM
Test build #95492 has finished for PR 22292 at commit
|
For future, let us keep a connection with #22233 that is the original one |
Test build #95526 has finished for PR 22292 at commit
|
jenkins, retest this, please |
Test build #95531 has finished for PR 22292 at commit
|
Thanks! Merged to master. |
What changes were proposed in this pull request?
I propose to remove one of
parmap
methods which accepts an execution context as a parameter. The method should be removed to eliminate any deadlocks that can occur ifparmap
is called recursively on thread pools restricted by size.