[
https://issues.apache.org/jira/browse/FLINK-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151979#comment-16151979
]
ASF GitHub Bot commented on FLINK-7078:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/4578
> Support fencing tokens to filter out outdated messages
> ------------------------------------------------------
>
> Key: FLINK-7078
> URL: https://issues.apache.org/jira/browse/FLINK-7078
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Labels: flip-6
> Fix For: 1.4.0
>
>
> In order to guard against split brain situations, it is important that RPC
> calls are guarded with a fencing token. The sender attaches his fencing token
> to a RPC message which is then used on the receiver side to compare against
> the expected fencing token. An example is the leader session ID which we
> attach to all critical RPC messages.
> So far, in the Flip-6 code base we send fencing tokens explicitly. This is
> not only cumbersome but also error-prone because you have to do it for all
> RPCs. Therefore, it would be better if we could automatically compare fencing
> tokens for a given RPC from a given source. This should ideally happen on the
> level of the RPC server.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
