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] [Closed] (FLINK-7458) Generalize GatewayRetriever for WebRuntimeMonitor
Date Mon, 18 Sep 2017 21:01:00 GMT

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

Till Rohrmann closed FLINK-7458.
       Resolution: Fixed
    Fix Version/s: 1.4.0

Fixed via 6ad0d3519585a825499245493f4bc77dac77d439

> Generalize GatewayRetriever for WebRuntimeMonitor
> -------------------------------------------------
>                 Key: FLINK-7458
>                 URL: https://issues.apache.org/jira/browse/FLINK-7458
>             Project: Flink
>          Issue Type: Improvement
>          Components: Distributed Coordination, Webfrontend
>    Affects Versions: 1.4.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>              Labels: flip-6
>             Fix For: 1.4.0
> Currently, all web frontend information can be retrieved from the {{JobManager}}. For
that, we have the {{JobManagerRetriever}} which listens to leader changes and always connects
to the leading {{JobManager}}. This gateway can then be used by the REST handlers. In the
future (with Flip-6) the information will be distributed across different components and multiple
components will have a REST endpoint. Due to that the REST handlers no longer can rely on
the {{JobManagerGateway}}. Instead they might connect to different entities which need to
be retrieved. In order to solve this problem, I propose to introduce a generalized gateway
retriever which allows to retrieve the {{RpcGateway}} for different components.

This message was sent by Atlassian JIRA

View raw message