You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/06/14 16:11:00 UTC
[jira] [Closed] (FLINK-9573) Check for leadership with leader
session id
[ https://issues.apache.org/jira/browse/FLINK-9573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-9573.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.5.1
1.6.0
Fixed via
1.6.0: 363de6b643689f64564270857f1daf7f6c59257f
1.5.1: 7286d0bc90b23e070a5e91e84325ad6a92f09bfa
> Check for leadership with leader session id
> -------------------------------------------
>
> Key: FLINK-9573
> URL: https://issues.apache.org/jira/browse/FLINK-9573
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.5.0, 1.6.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Fix For: 1.6.0, 1.5.1
>
>
> In order to check whether a {{LeaderContender}} is still the leader, it is not sufficient to simply provide a {{LeaderElectionService#hasLeadership()}}. Instead, we should extend this method to also take the leader session id as a parameter to distinguish between different calls from the same leader contender with different leader session ids.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)