You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/09/20 12:46:00 UTC

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

Till Rohrmann created FLINK-7655:
------------------------------------

             Summary: 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


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)