[
https://issues.apache.org/jira/browse/FLINK-24038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481006#comment-17481006
]
Matthias Pohl edited comment on FLINK-24038 at 1/24/22, 11:00 AM:
------------------------------------------------------------------
I changed the FLINK-25432 link from "blocks" to "relates to" because we're
considering the order of cleanup (i.e. {{JobMaster}} needs to be closed before
cleaning up the {{{}HighAvailabilityServices{}}}) in {{FLINK-25432}} now.
This invariant can be removed as soon as we remove the old component-based
leader election entirely. Currently, FLINK-24038 implements this feature in a
way that it's configurable.
was (Author: mapohl):
I changed the FLINK-25432 link from "blocks" to "relates to" because we're
considering the order of cleanup (i.e. \{{JobMaster}} needs to be closed before
cleaning up the \{{HighAvailabilityServices}}) now.
This invariant can be removed as soon as we remove the old component-based
leader election entirely. Currently, FLINK-24038 implements this feature in a
way that it's configurable.
> DispatcherResourceManagerComponent fails to deregister application if no
> leading ResourceManager
> ------------------------------------------------------------------------------------------------
>
> Key: FLINK-24038
> URL: https://issues.apache.org/jira/browse/FLINK-24038
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.14.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> With FLINK-21667 we introduced a change that can cause the
> {{DispatcherResourceManagerComponent}} to fail when trying to stop the
> application. The problem is that the {{DispatcherResourceManagerComponent}}
> needs a leading {{ResourceManager}} to successfully execute the
> stop/deregister application call. If this is not the case, then it will fail
> fatally. In the case of multiple standby JobManager processes it can happen
> that the leading {{ResourceManager}} runs somewhere else.
> I do see two possible solutions:
> 1. Run the leader election process for the whole JobManager process
> 2. Move the registration/deregistration of the application out of the
> {{ResourceManager}} so that it can be executed w/o a leader
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
