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 2017/09/21 23:01:00 UTC

[jira] [Closed] (FLINK-7655) Revisit default non-leader id for FencedRpcEndpoints

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

Till Rohrmann closed FLINK-7655.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0

Fixed via 42cc3a2a9c41dda7cf338db36b45131db9150674

> Revisit default non-leader id for FencedRpcEndpoints
> ----------------------------------------------------
>
>                 Key: FLINK-7655
>                 URL: https://issues.apache.org/jira/browse/FLINK-7655
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination
>    Affects Versions: 1.4.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Minor
>              Labels: flip-6
>             Fix For: 1.4.0
>
>
> Currently, when a {{FencedRpcEndpoint}} loses leadership, we set its leader id to a random value. This can be problematic, even though it's unlikely, because we might set it to a value which is used somewhere else (e.g. the currently valid leader id). I think it would  be better to simply set the leader id to {{null}} in order to properly encode that the {{FencedRpcEndpoint}} is no longer a leader.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)