You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/10/22 18:16:28 UTC
[jira] [Commented] (SPARK-11252) ExternalShuffleClient should
release connection after it had completed to fetch blocks from yarn's
NameManager
[ https://issues.apache.org/jira/browse/SPARK-11252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969375#comment-14969375 ]
Apache Spark commented on SPARK-11252:
--------------------------------------
User 'lianhuiwang' has created a pull request for this issue:
https://github.com/apache/spark/pull/9227
> ExternalShuffleClient should release connection after it had completed to fetch blocks from yarn's NameManager
> --------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-11252
> URL: https://issues.apache.org/jira/browse/SPARK-11252
> Project: Spark
> Issue Type: Bug
> Components: Shuffle, YARN
> Reporter: Lianhui Wang
>
> ExternalShuffleClient of executors reserve its connection with yarn's NodeManager until application has been completed. so it will make NodeManager has many socket connections.
> in order to reduce network pressure of NodeManager's shuffleService, after registerWithShuffleServer or fetchBlocks have been completed in ExternalShuffleClient, connection for shuffleService needs to be closed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org