flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-7078) Support fencing tokens to filter out outdated messages
Date Mon, 03 Jul 2017 22:24:00 GMT
Till Rohrmann created FLINK-7078:
------------------------------------

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


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)

Mime
View raw message