[
https://issues.apache.org/jira/browse/FLINK-24380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421993#comment-17421993
]
Yang Wang commented on FLINK-24380:
-----------------------------------
Fixed via:
master(1.15): b9fbdf8c906aea4fce8881a7b8fb13619f4157ea
release-1.14: ee4776799ddfca0a7554fbc2d78d640a16eb6ab4
release-1.13: 5452dccfb4e1e80a627647caea63aba3bda0fa79
> Flink should handle the state transition of the pod from Pending to Failed
> --------------------------------------------------------------------------
>
> Key: FLINK-24380
> URL: https://issues.apache.org/jira/browse/FLINK-24380
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.14.0, 1.13.2
> Reporter: Yangze Guo
> Assignee: Yangze Guo
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.3, 1.15.0, 1.14.1
>
>
> In K8s, there is five phases in pod's lifecycle: Pending, Running, Secceeded,
> Failed and Unknown. Currently, Flink does not handle the state transition of
> the pod from Pending to Failed. If a pod failed from Pending by `OutOfCPU` or
> `OutOfMem`, it will never be released and Flink keep waiting for it.
> To fix this issue, Flink should terminate the pod in Failed phase proactively.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
