[jira] [Updated] (FLINK-14287) Decouple leader address from LeaderContender

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot updated FLINK-14287:
-----------------------------------
    Labels: pull-request-available  (was: )

> Decouple leader address from LeaderContender
> --------------------------------------------
>
>                 Key: FLINK-14287
>                 URL: https://issues.apache.org/jira/browse/FLINK-14287
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>
> At the moment, the {{LeaderContender}} need to know the address of the leader before it has gained leadership. This is problematic if one wants to decouple the leader election from the actual leader component which will potentially only be created after the leadership has been gained. If this is the case, then it is not always possible to know the address of the actual leader component before gaining the leadership.
> In order to solve this problem, I propose to change the interface of {{LeaderElectionService#confirmLeadership(UUID)}} to {{LeaderElectionService#confirmLeadership(UUID, String)}} where the second parameter is the leader address under which the leader component is reachable.



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