You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/05/22 06:28:00 UTC

[jira] [Updated] (FLINK-24713) Postpone resourceManager serving after the recovery phase has finished

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

ASF GitHub Bot updated FLINK-24713:
-----------------------------------
    Labels: pull-request-available  (was: )

> Postpone resourceManager serving after the recovery phase has finished
> ----------------------------------------------------------------------
>
>                 Key: FLINK-24713
>                 URL: https://issues.apache.org/jira/browse/FLINK-24713
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.14.0
>            Reporter: Aitozi
>            Assignee: Aitozi
>            Priority: Major
>              Labels: pull-request-available
>
> When ResourceManager started, JobManger will connect to the ResourceManager, this means the ResourceManager will begin to try serve the resource requests from SlotManager.
> If ResourceManager failover, although it will try to recover the pod / container from previous attempt, But new resource requirements may happen before the old taskManger register to slotManager. 
> In this case, it may double the required taskManager when jobManager failover. We may need a mechanism to postpone resourceManager serving after the recovery phase has finished



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