[
https://issues.apache.org/jira/browse/FLINK-19289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198357#comment-17198357
]
Yi Tang edited comment on FLINK-19289 at 9/18/20, 2:33 PM:
-----------------------------------------------------------
Exactly, it's good to filter and remove terminated pods before starting to
watch.
But, there is a gap (maybe very short) btw listing and watching pods. So just
filter before is not *absolutely* right. What do you think?
was (Author: yittg):
Exactly, it's good to filter and remove terminated pods before starting to
watch.
> 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)
