[
https://issues.apache.org/jira/browse/FLINK-27737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song updated FLINK-27737:
---------------------------------
Summary: Remove legacy support for unfenced executor in FencedRpcEndpoint
(was: Clean the outdated comments and unfencedMainExecutor)
> Remove legacy support for unfenced executor in FencedRpcEndpoint
> ----------------------------------------------------------------
>
> Key: FLINK-27737
> URL: https://issues.apache.org/jira/browse/FLINK-27737
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Coordination
> Reporter: Aitozi
> Priority: Major
>
> There are 2 main thread executors in {{FencedRpcEndpoint}}, the fenced- and
> unfenced-. The fenced executor was available only during a specific leader
> session, while the unfenced executor was used for actions out of a leader
> session (e.g., during the initialization). This is no longer needed because
> currently for all the fenced endpoints ({{Dispatcher}}, {{JobMaster}} and
> {{ResourceManager}}), the leader election finishes before the endpoints are
> initiated.
> In this ticket we propose to remove the legacy codes for supporting unfenced
> executor and updating fenced tokens, as well as to simplify the type
> hierarchy of {{FencedRpcEndpoint}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
