You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/11/01 23:20:35 UTC

[jira] [Reopened] (SPARK-4183) Enable Netty-based BlockTransferService by default

     [ https://issues.apache.org/jira/browse/SPARK-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Wendell reopened SPARK-4183:
------------------------------------

Reverted this due to a test issue - seems like some state is not getting cleaned up.

> Enable Netty-based BlockTransferService by default
> --------------------------------------------------
>
>                 Key: SPARK-4183
>                 URL: https://issues.apache.org/jira/browse/SPARK-4183
>             Project: Spark
>          Issue Type: Bug
>            Reporter: Aaron Davidson
>            Assignee: Aaron Davidson
>             Fix For: 1.2.0
>
>
> Spark's NettyBlockTransferService relies on Netty to achieve high performance and zero-copy IO, which is a big simplification over the manual connection management that's done in today's NioBlockTransferService. Additionally, the core functionality of the NettyBlockTransferService has been extracted out of spark core into the "network" package, with the intention of reusing this code for SPARK-3796 ([PR #3001|https://github.com/apache/spark/pull/3001/files#diff-54]).
> We should turn NettyBlockTransferService on by default in order to improve debuggability and stability of the network layer (which has historically been more challenging with the current BlockTransferService).



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