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

Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/07/05 09:55:00 UTC

[jira] [Updated] (FLINK-17273) Fix not calling ResourceManager#closeTaskManagerConnection in KubernetesResourceManager in case of registered TaskExecutor failure

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

Robert Metzger updated FLINK-17273:
-----------------------------------
    Fix Version/s:     (was: 1.11.0)
                   1.12.0

> Fix not calling ResourceManager#closeTaskManagerConnection in KubernetesResourceManager in case of registered TaskExecutor failure
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-17273
>                 URL: https://issues.apache.org/jira/browse/FLINK-17273
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes, Runtime / Coordination
>    Affects Versions: 1.10.0, 1.10.1
>            Reporter: Canbin Zheng
>            Assignee: Canbin Zheng
>            Priority: Major
>             Fix For: 1.12.0
>
>
> At the moment, the {{KubernetesResourceManager}} does not call the method of {{ResourceManager#closeTaskManagerConnection}} once it detects that a currently registered task executor has failed. This ticket propoeses to fix this problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)