You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Canbin Zheng (Jira)" <ji...@apache.org> on 2020/04/16 06:32:00 UTC
[jira] [Updated] (FLINK-17177) Handle ERROR event correctly in
KubernetesResourceManager#onError
[ https://issues.apache.org/jira/browse/FLINK-17177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Canbin Zheng updated FLINK-17177:
---------------------------------
Summary: Handle ERROR event correctly in KubernetesResourceManager#onError (was: Handle Pod ERROR event correctly in KubernetesResourceManager#onError)
> Handle ERROR event correctly in KubernetesResourceManager#onError
> -----------------------------------------------------------------
>
> Key: FLINK-17177
> URL: https://issues.apache.org/jira/browse/FLINK-17177
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0, 1.10.1
> Reporter: Canbin Zheng
> Priority: Major
> Fix For: 1.11.0
>
>
> Currently, once we receive an *ERROR* event that is sent from the K8s API server via the K8s {{Watcher}}, then {{KubernetesResourceManager#onError}} will handle it by calling the {{KubernetesResourceManager#removePodIfTerminated}}. This is incorrect since the *ERROR* event ** indicates an exception in the HTTP layer that is caused by the K8s Server, which means the previously created {{Watcher}} is no longer available and we should re-create a new {{Watcher}} immediately.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)