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

Posted to issues@flink.apache.org by "vinoyang (JIRA)" <ji...@apache.org> on 2018/10/30 01:31:00 UTC

[jira] [Assigned] (FLINK-10718) Use IO executor in RpcService for message serialization

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

vinoyang reassigned FLINK-10718:
--------------------------------

    Assignee: vinoyang

> Use IO executor in RpcService for message serialization
> -------------------------------------------------------
>
>                 Key: FLINK-10718
>                 URL: https://issues.apache.org/jira/browse/FLINK-10718
>             Project: Flink
>          Issue Type: Improvement
>          Components: Local Runtime
>    Affects Versions: 1.5.5, 1.6.2, 1.7.0
>            Reporter: Till Rohrmann
>            Assignee: vinoyang
>            Priority: Major
>             Fix For: 1.7.0
>
>
> The {{AkkaInvocationHandler}} and once FLINK-10251 has been merged also the {{AkkaRpcActor}} serialize their remote RPC messages before sending them. This happens in the calling thread which can be a main thread of another {{RpcEndpoint}}. Depending on the de-/serialization time, this can be considered a blocking operation. Thus, I propose to introduce an IO executor which is being used for the serialization of the messages. This will make the {{RpcService}} abstraction more scalable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)