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

Posted to issues@flink.apache.org by "Peng Yuan (Jira)" <ji...@apache.org> on 2022/11/16 04:15:00 UTC

[jira] [Updated] (FLINK-30036) Force delete pod when k8s node is not ready

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

Peng Yuan updated FLINK-30036:
------------------------------
    Description: 
When the K8s node is in the NotReady state, the taskmanager pod scheduled on it is always in the terminating state. When the flink cluster has a strict quota, the terminating pod will hold the resources all the time. As a result, the new taskmanager pod cannot apply for resources and cannot be started.

 

> Force delete pod when  k8s node is not ready
> --------------------------------------------
>
>                 Key: FLINK-30036
>                 URL: https://issues.apache.org/jira/browse/FLINK-30036
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>            Reporter: Peng Yuan
>            Priority: Major
>
> When the K8s node is in the NotReady state, the taskmanager pod scheduled on it is always in the terminating state. When the flink cluster has a strict quota, the terminating pod will hold the resources all the time. As a result, the new taskmanager pod cannot apply for resources and cannot be started.
>  



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