[
https://issues.apache.org/jira/browse/FLINK-30462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Pohl updated FLINK-30462:
----------------------------------
Parent: FLINK-26522
Issue Type: Sub-task (was: Bug)
> DefaultMultipleComponentLeaderElectionService saves wrong leader session ID
> ---------------------------------------------------------------------------
>
> Key: FLINK-30462
> URL: https://issues.apache.org/jira/browse/FLINK-30462
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.16.0, 1.17.0, 1.15.3
> Reporter: Matthias Pohl
> Assignee: Matthias Pohl
> Priority: Critical
> Labels: pull-request-available
>
> We save a UUID in
> [DefaultMultipleComponentLeaderElectionService:195|https://github.com/apache/flink/blob/0290715a57b8d243586ab747b0cd2416c8081012/flink-runtime/src/main/java/org/apache/flink/runtime/leaderelection/DefaultMultipleComponentLeaderElectionService.java#L195]
> but use a different one for granting the leadership to each of the
> components (see
> [DefaultMultipleComponentLeaderElectionService:199|https://github.com/apache/flink/blob/0290715a57b8d243586ab747b0cd2416c8081012/flink-runtime/src/main/java/org/apache/flink/runtime/leaderelection/DefaultMultipleComponentLeaderElectionService.java#L199]).
> We reach an inconsistent state if the JM acquired the leadership before
> another component registers itself at the
> {{MultipleComponentLeaderElectionService}}. In that case, a different session
> ID is passed than the one that is set for components that have been
> registered before the leadership was acquired by the JobManager. That could
> be the case for JobMaster leadershipt.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
