[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 ] Flink Jira Bot updated FLINK-30036: --- Labels: auto-deprioritized-major pull-request-available (was: pull-request-available stale-major) Priority: Minor (was: Major) This issue was labeled "stale-major" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > 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: Minor > Labels: auto-deprioritized-major, pull-request-available > Attachments: image-2022-11-17-10-25-59-945.png > > > 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)
[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 ] Flink Jira Bot updated FLINK-30036: --- Labels: pull-request-available stale-major (was: pull-request-available) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > 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 > Labels: pull-request-available, stale-major > Attachments: image-2022-11-17-10-25-59-945.png > > > 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)
[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: -- Attachment: image-2022-11-17-10-25-59-945.png > 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 > Labels: pull-request-available > Attachments: image-2022-11-17-10-25-59-945.png > > > 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)
[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 ] ASF GitHub Bot updated FLINK-30036: --- Labels: pull-request-available (was: ) > 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 > Labels: pull-request-available > > 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)
[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)
