[
https://issues.apache.org/jira/browse/FLINK-14261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939723#comment-16939723
]
Zili Chen commented on FLINK-14261:
-----------------------------------
Permanently Fenced RpcEndpoint could be a good intermediate abstraction.
Since all Fenced RpcEndpoint participants leader election before(this is where
the requirement of fencing tech comes from), once leader election always
happens outside of RpcEndpoint we can even safely remove leader session id
field because now message are fenced to different actors naturally.
> Add support for permanently fenced RpcEndpoints
> -----------------------------------------------
>
> Key: FLINK-14261
> URL: https://issues.apache.org/jira/browse/FLINK-14261
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If leader election happens outside of a {{RpcEndpoint}} we no longer need to
> set the fencing token after the endpoint has been started. This can simplify
> the internal functioning of the endpoint. In order to support this feature, I
> propose to add a {{PermanentlyFencedRpcEndpoint}} which is started with a
> fixed fencing token.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)