[
https://issues.apache.org/jira/browse/FLINK-17273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091096#comment-17091096
]
Xintong Song commented on FLINK-17273:
--------------------------------------
+1 for revisiting the boundary between {{ResourceManager}} and its deployment
specific implementations.
I think this would help deduplicating the worker lifecycle control flow across
deployments. The RM implementations should only handles the minimum set of
deployment specific API/behavior differences.
> 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.11.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)
