[
https://issues.apache.org/jira/browse/FLINK-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118389#comment-14118389
]
Henry Saputra commented on FLINK-1019:
--------------------------------------
Both TaskManagers (TM) to the JobManager (JM) are called from Flink client
which exposes API to the application program.
I am thinking this is going to be lower level communication and we could use
Netty instead which lower level and perform more efficient than Akka remote.
The other good thing is that Netty is in Java.
>From dev@ list, Stephan said he has been using Akka to do ExecutionGraph and
>Scheduler, which will be internal components and perfect solutions for Akka to
>provide so-sharing framework instead of executor service. In this case, we
>could add like Scala service bridge to allow smoother transition between
>existing Java code and Scala code that communicate with Akka.
I did the similar thing in my previous job to bridge between Scala and Java
world for internal services.
Just my 2-cents
> Rework RPC service
> ------------------
>
> Key: FLINK-1019
> URL: https://issues.apache.org/jira/browse/FLINK-1019
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Runtime
> Reporter: Ufuk Celebi
>
> There is work going on to improve the RPC service by using [Akka|akka.io]. I
> couldn't find a issue for it.
> Could one of the two people working on it ([~StephanEwen] and [~asteriosk])
> please give an overview of the changes and a status update?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
