flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-4346) Implement basic RPC abstraction
Date Wed, 10 Aug 2016 10:12:21 GMT

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

Till Rohrmann updated FLINK-4346:
---------------------------------
    Description: 
As part of refactoring of the cluster management, we can introduce a new RPC abstraction on
top of our Akka-based distributed coordination.

It should address the following issues:

  - Add type safety to the sender and receiver of messages. We want proper types methods to
be called, rather than haveing generic message types and pattern matching everywhere. This
is similar to typed actors.

  - Make the message receivers testable without involving actors, i.e. the methods should
be callable directly. When used with other component, the receiver will be wrapped in an actor
that calls the methods based on received messages.

  - We want to keep the paradigm of single-threaded execution per "actor"

There is some basic code layout in the following branch and commit:

https://github.com/apache/flink/tree/flip-6/flink-runtime/src/main/java/org/apache/flink/runtime/rpc

  was:
As part of refactoring of the cluster management, we can introduce a new RPC abstraction on
top of our Akka-based distributed coordination.

It should address the following issues:

  - Add type safety to the sender and receiver of messages. We want proper types methods to
be called, rather than haveing generic message types and pattern matching everywhere. This
is similar to typed actors.

  - Make the message receivers testable without involving actors, i.e. the methods should
be callable directly. When used with other component, the receiver will be wrapped in an actor
that calls the methods based on received messages.

  - We want to keep the paradigm of single-threaded execution per "actor"

There is some basic code layout in the following branch and commit:

https://github.com/apache/flink/tree/f1b45d320181284eca64126ba04f010e23757e38/flink-runtime/src/main/java/org/apache/flink/runtime/rpc


> Implement basic RPC abstraction
> -------------------------------
>
>                 Key: FLINK-4346
>                 URL: https://issues.apache.org/jira/browse/FLINK-4346
>             Project: Flink
>          Issue Type: New Feature
>          Components: Distributed Coordination
>            Reporter: Stephan Ewen
>            Assignee: Till Rohrmann
>
> As part of refactoring of the cluster management, we can introduce a new RPC abstraction
on top of our Akka-based distributed coordination.
> It should address the following issues:
>   - Add type safety to the sender and receiver of messages. We want proper types methods
to be called, rather than haveing generic message types and pattern matching everywhere. This
is similar to typed actors.
>   - Make the message receivers testable without involving actors, i.e. the methods should
be callable directly. When used with other component, the receiver will be wrapped in an actor
that calls the methods based on received messages.
>   - We want to keep the paradigm of single-threaded execution per "actor"
> There is some basic code layout in the following branch and commit:
> https://github.com/apache/flink/tree/flip-6/flink-runtime/src/main/java/org/apache/flink/runtime/rpc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message