[
https://issues.apache.org/jira/browse/FLINK-19289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198239#comment-17198239
]
Yi Tang commented on FLINK-19289:
---------------------------------
bq. Flink should receive not only a ADDED event, but also the MODIFIED/ERROR
events, thus triggering removal of the pods.
I believe only a ADDED event will be received, it's about the k8s resource
watching logic.
bq. Have you verified that the error pod is not removed even after the JM
successfully recovered for a while?
Yeah, the JM do nothing with the error pod,
i try to update some not important fields of the error pod, then it can be
removed right now.
> K8s resource manager terminated pod garbage collection
> ------------------------------------------------------
>
> Key: FLINK-19289
> URL: https://issues.apache.org/jira/browse/FLINK-19289
> Project: Flink
> Issue Type: Bug
> Reporter: Yi Tang
> Priority: Minor
>
> For a senario,
> During JM is down (no JM is running), a TM down with error (for reasons from
> the node or TM inner), then an Error pod present there. After one JM recover,
> it will receive a ADDED event about this pod and do nothing.
> We should deal with this case in `onAdded` callback properly, I think.
> cc [~xintongsong].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
