GitHub user tgravescs opened a pull request:
https://github.com/apache/spark/pull/2484
[SPARK-3632] ConnectionManager can run out of receive threads with
authentication on
If you turn authentication on and you are using a lot of executors. There
is a chance that all the of the threads in the handleMessageExecutor could be
waiting to send a message because they are blocked waiting on authentication to
happen. This can cause a temporary deadlock until the connection times out.
To fix it, I got rid of the wait/notify and use a single outbox but only
send security messages from it until authentication has completed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgravescs/spark cm_threads_auth
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/2484.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2484
----
commit 4d7f8f5f0d2de2e43ce2be013e52086d5beaa5a9
Author: Thomas Graves <[email protected]>
Date: 2014-09-21T20:16:09Z
Change to not use wait/notify while waiting for authentication
commit 081b765bc291e96300bfb521a678812289b31962
Author: Thomas Graves <[email protected]>
Date: 2014-09-22T02:36:43Z
cleanup
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
