You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Shixiong Zhu (JIRA)" <ji...@apache.org> on 2015/10/21 13:26:27 UTC
[jira] [Comment Edited] (SPARK-11098) RPC message ordering is not
guaranteed
[ https://issues.apache.org/jira/browse/SPARK-11098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966657#comment-14966657 ]
Shixiong Zhu edited comment on SPARK-11098 at 10/21/15 11:26 AM:
-----------------------------------------------------------------
[~vanzin] Vanzin Sorry I didn't realize you were not working on this one...
I just sent a PR to fix the message ordering issue. I think we should guarantee that if using the same RpcEndpointRef to send multiple messages in the same thread, the receiver side (ThreadSafeRpcEndpoint) should see these messages in the same order.
was (Author: zsxwing):
[~vanzin] Vanzin Sorry I didn't realize you were not working on this one...
I just sent a PR to fix the message ordering issue. I think we should guarantee that if using the same RpcEndpointRef to send multiple messages in the same thread, the receiver side should see these messages in the same order.
> RPC message ordering is not guaranteed
> --------------------------------------
>
> Key: SPARK-11098
> URL: https://issues.apache.org/jira/browse/SPARK-11098
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Reporter: Reynold Xin
>
> NettyRpcEnv doesn't guarantee message delivery order since there are multiple threads sending messages in clientConnectionExecutor thread pool. We should fix that.
--
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