flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-22597) JobMaster cannot be restarted
Date Fri, 07 May 2021 15:29:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-22597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Till Rohrmann updated FLINK-22597:
----------------------------------
    Description: Since we are reusing the {{DefaultLeaderRetrievalService}} for finding the
resource manager in the {{JobMaster}} and since the leader retrieval service cannot be reused,
it is not possible to restart the {{JobMaster}}. This causes Flink to fail in case that the
{{JobMaster}} regains the leadership in Flink versions <= 1.12. The problem no longer occurs
for newer versions because of FLINK-11719.  (was: Since we are reusing the {{DefaultLeaderRetrievalService}}
for finding the resource manager in the {{JobMaster}} and since the leader retrieval service
cannot be reused, it is not possible to restart the {{JobMaster}}. This causes Flink to fail
in case that the {{JobMaster}} regains the leadership in Flink versions <= 1.12.)

> JobMaster cannot be restarted
> -----------------------------
>
>                 Key: FLINK-22597
>                 URL: https://issues.apache.org/jira/browse/FLINK-22597
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.11.3, 1.12.3
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.4, 1.12.4
>
>
> Since we are reusing the {{DefaultLeaderRetrievalService}} for finding the resource manager
in the {{JobMaster}} and since the leader retrieval service cannot be reused, it is not possible
to restart the {{JobMaster}}. This causes Flink to fail in case that the {{JobMaster}} regains
the leadership in Flink versions <= 1.12. The problem no longer occurs for newer versions
because of FLINK-11719.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message