[jira] [Comment Edited] (FLINK-22816) Investigate feasibility of supporting multiple RM leader sessions within JM process

["Xintong Song (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-22816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528486#comment-17528486 ] 

Xintong Song edited comment on FLINK-22816 at 4/27/22 2:33 AM:
---------------------------------------------------------------

Subsumed by FLINK-23240


was (Author: xintongsong):
Subsumed by FLINK-21667

> Investigate feasibility of supporting multiple RM leader sessions within JM process
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-22816
>                 URL: https://issues.apache.org/jira/browse/FLINK-22816
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Xintong Song
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> In FLINK-21667, we decoupled RM leadership and lifecycle managements. RM is not started after obtaining leadership, and stopped on losing leadership.
> Ideally, we may start and stop multiple RMs, as the process obtains and loses leadership. However, as discussed in the [PR|https://github.com/apache/flink/pull/15524#pullrequestreview-663987547], having a process to start multiple RMs may cause problems in some deployment modes. E.g., repeated AM registration is not allowed on Yarn.
> We need to investigate for all deployments that:
> - Whether having multiple leader sessions causes problems.
> - If it does, what can we do to solve the problem.
> For information, multi-leader-session support for RM has been implemented in FLINK-21667, but is disabled by default. To enable, add the system property "flink.tests.enable-rm-multi-leader-session". 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)