You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "TisonKun (JIRA)" <ji...@apache.org> on 2019/02/26 03:18:00 UTC

[jira] [Updated] (FLINK-11749) Returns the stored leadership info on ZooKeeperLeaderRetrievalService started

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

TisonKun updated FLINK-11749:
-----------------------------
    Summary: Returns the stored leadership info on ZooKeeperLeaderRetrievalService started  (was: Returns the stored leadership on ZooKeeperLeaderRetrievalService stated)

> Returns the stored leadership info on ZooKeeperLeaderRetrievalService started
> -----------------------------------------------------------------------------
>
>                 Key: FLINK-11749
>                 URL: https://issues.apache.org/jira/browse/FLINK-11749
>             Project: Flink
>          Issue Type: Improvement
>          Components: Distributed Coordination
>    Affects Versions: 1.9.0
>            Reporter: TisonKun
>            Assignee: TisonKun
>            Priority: Major
>             Fix For: 1.9.0
>
>
> Currently, such as in {{JobMaster}}, if we stop a {{ZooKeeperLeaderRetrievalService}} and restart it, because the cached node data isn't change, we have to manually flush it.
> I propose on {{ZooKeeperLeaderRetrievalService}} stated, get {{ChildData}} from {{NodeCache}} and if the data isn't null, generate LeadershipInfo(Address and UUID) and notify the listener.
> cc [~till.rohrmann]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)