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/09/20 01:10:00 UTC

[jira] [Issue Comment Deleted] (FLINK-4233) Simplify leader election / leader session ID assignment

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

TisonKun updated FLINK-4233:
----------------------------
    Comment: was deleted

(was: Further, if it is assumed that there are never too many contenders, in FLINK-10333 we can adopt the unoptimized version of leader election, i.e., create the universe leader node, and if fails, wait for its deletion. Then we trade off performance(no impact) for simplicity.)

> Simplify leader election / leader session ID assignment
> -------------------------------------------------------
>
>                 Key: FLINK-4233
>                 URL: https://issues.apache.org/jira/browse/FLINK-4233
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.0.3
>            Reporter: Stephan Ewen
>            Priority: Major
>
> Currently, there are two separate actions and znodes involved in leader election and communication of the leader session ID and leader URL.
> This leads to some quite elaborate code that tries to make sure that the leader session ID and leader URL always eventually converge to those of the leader.
> It is simpler to just encode both the ID and the URL into an id-string that is attached to the leader latch znode. One would have to create a new leader latch each time a contender re-applies for leadership.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)