[
https://issues.apache.org/jira/browse/FLINK-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-4233:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
