You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2015/07/08 16:55:05 UTC
[jira] [Created] (FLINK-2329) Refactor RPCs from within the
ExecutionGraph
Till Rohrmann created FLINK-2329:
------------------------------------
Summary: Refactor RPCs from within the ExecutionGraph
Key: FLINK-2329
URL: https://issues.apache.org/jira/browse/FLINK-2329
Project: Flink
Issue Type: Sub-task
Reporter: Till Rohrmann
Assignee: Till Rohrmann
Currently, we store an {{ActorRef}} of the TaskManager into an {{Instance}} object. This {{ActorRef}} is used from within {{Executions}} to interact with the {{TaskManager}}. This is not a nice abstraction since it does not hide implementation details.
Since we need to add a leader session ID to messages sent by the {{Executions}} in order to support high availability, we would need to make the leader session ID available to the {{Execution}}. A better solution seems to be to replace the direct {{ActorRef}} interaction with an instance gateway abstraction which encapsulates the communication logic. Having such an abstraction, it will be easy to decorate messages transparently with a leader session ID. Therefore, I propose to refactor the current {{Instance}} communication and to introduce an {{InstanceGateway}} abstraction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)