[
https://issues.apache.org/jira/browse/SPARK-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reynold Xin updated SPARK-6578:
-------------------------------
Priority: Blocker (was: Critical)
> Outbound channel in network library is not thread-safe, can lead to fetch
> failures
> ----------------------------------------------------------------------------------
>
> Key: SPARK-6578
> URL: https://issues.apache.org/jira/browse/SPARK-6578
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.3.0
> Reporter: Marcelo Vanzin
> Assignee: Marcelo Vanzin
> Priority: Blocker
>
> There is a very narrow race in the outbound channel of the network library.
> While netty guarantees that the inbound channel is thread-safe, the same is
> not true for the outbound channel: multiple threads can be writing and
> running the pipeline at the same time.
> This leads to an issue with MessageEncoder and the optimization it performs
> for zero-copy of file data: since a single RPC can be broken into multiple
> buffers (for , example when replying to a chunk request), if you have
> multiple threads writing these RPCs then they can be mixed up in the final
> socket. That breaks framing and will cause the receiving side to not
> understand the messages.
> Patch coming up shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
