[
https://issues.apache.org/jira/browse/FLINK-22816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22816:
-----------------------------------
Labels: stale-major (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: stale-major
>
> 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.3.4#803005)
