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 2019/02/28 11:07:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16780384#comment-16780384 ] 

Till Rohrmann commented on FLINK-11749:
---------------------------------------

Could give me a bit more context [~Tison]. What is exactly the problem we try to improve here? Is it mainly code simplification?

> 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: Runtime / 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)