GitHub user lianhuiwang opened a pull request:
https://github.com/apache/spark/pull/9227
[spark-11252][network]ShuffleClient should release connection after
fetching blocks had been completed for external shuffle
with yarn's external shuffle, ExternalShuffleClient of executors reserve
its connections for yarn's NodeManager until application has been completed. so
it will make NodeManager and executors have many socket connections.
in order to reduce network pressure of NodeManager's shuffleService, after
registerWithShuffleServer or fetchBlocks have been completed in
ExternalShuffleClient, connection for NM's shuffleService needs to be
closed.@andrewor14 @rxin @vanzin
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lianhuiwang/spark spark-11252
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/9227.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 #9227
----
commit 6094ad7cfb567d0025b8f369d2365dd089c210ea
Author: Lianhui Wang <[email protected]>
Date: 2015-10-22T16:09:35Z
release connection for external shuffle
----
---
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]
