spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Ash (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-4837) NettyBlockTransferService does not abide by spark.blockManager.port config option
Date Mon, 15 Dec 2014 18:56:13 GMT

    [ https://issues.apache.org/jira/browse/SPARK-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247030#comment-14247030
] 

Andrew Ash commented on SPARK-4837:
-----------------------------------

Ok that's fair -- a release note and targeting 1.2.1 sounds good.

Draft language for that release note could be:

- Spark 1.2.0 changes the default block transfer service to NettyBlockTransferService, a higher
performance block transfer service than the old XYZBlockTransferService.  The new transfer
service does not yet respect `spark.blockManager.port` so deployments needing full control
of Spark's network ports in 1.2.0 should temporarily set `spark.abc=xyz` and watch SPARK-4837

> NettyBlockTransferService does not abide by spark.blockManager.port config option
> ---------------------------------------------------------------------------------
>
>                 Key: SPARK-4837
>                 URL: https://issues.apache.org/jira/browse/SPARK-4837
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.2.0
>            Reporter: Aaron Davidson
>            Assignee: Aaron Davidson
>            Priority: Blocker
>
> The NettyBlockTransferService always binds to a random port, and does not use the spark.blockManager.port
config as specified.



--
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


Mime
View raw message