You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2019/07/19 09:29:00 UTC
[jira] [Closed] (FLINK-13186) Remove dispatcherRetrievalService and
dispatcherLeaderRetriever from RestClusterClient
[ https://issues.apache.org/jira/browse/FLINK-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-13186.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.10.0
master: f7624518a9a89ef8a3ca2f9fa12d0859f5e72096
> Remove dispatcherRetrievalService and dispatcherLeaderRetriever from RestClusterClient
> --------------------------------------------------------------------------------------
>
> Key: FLINK-13186
> URL: https://issues.apache.org/jira/browse/FLINK-13186
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Reporter: vinoyang
> Assignee: vinoyang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In {{RestClusterClient}}, it contains two components: dispatcherRetrievalService which is the instance of {{LeaderRetrievalService}} and dispatcherLeaderRetriever which is the instance of {{LeaderRetriever}}. Both of them start in {{startLeaderRetrievers}} method and stop in {{shutdown}} method. It seems they are not necessary. IMO, we can remove them.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)