You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/08/11 11:50:00 UTC
[jira] [Closed] (FLINK-7381) Decouple WebRuntimeMonitor from
ActorGateway
[ https://issues.apache.org/jira/browse/FLINK-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-7381.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Fixed via 9f790d3efe5e8267da05eb97bbe07ca8a0f859fe
> Decouple WebRuntimeMonitor from ActorGateway
> --------------------------------------------
>
> Key: FLINK-7381
> URL: https://issues.apache.org/jira/browse/FLINK-7381
> Project: Flink
> Issue Type: Sub-task
> Components: Webfrontend
> Affects Versions: 1.4.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Labels: flip-6
> Fix For: 1.4.0
>
>
> The {{WebRuntimeMonitor}} has a hard wired dependency on the {{ActorGateway}} in order to communicate with the {{JobManager}}. In order to make it work with the {{JobMaster}} (Flip-6), we have to abstract this dependency away. I propose to add a {{JobManagerGateway}} interface which can be implemented using Akka for the old {{JobManager}} code. The Flip-6 {{JobMasterGateway}} can then directly inherit from this interface.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)