[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
