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 2024/03/07 09:00:00 UTC

[jira] [Updated] (FLINK-34524) Scale down JobManager deployment to 0 before deletion

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

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

> Scale down JobManager deployment to 0 before deletion
> -----------------------------------------------------
>
>                 Key: FLINK-34524
>                 URL: https://issues.apache.org/jira/browse/FLINK-34524
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Major
>              Labels: pull-request-available
>
> We recently improved the JM deployment deletion mechanism, however it seems like task manager pod deletion can get stuck sometimes for a couple of minutes in native mode if we simply try to delete everything at once.
> It speeds up the process and leads to cleaner shutdown if we scale down the JM deployment to 0 (shutting down the JM pods first) and then perform the deletion.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)