[
https://issues.apache.org/jira/browse/FLINK-26695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508053#comment-17508053
]
Yang Wang commented on FLINK-26695:
-----------------------------------
Just like [~mapohl] said, we already have the retry logic in the Dispatcher for
job related cleanup. As for the cluster cleanup, maybe FLIP-194[1] has also
covered.
[1].
https://cwiki.apache.org/confluence/display/FLINK/FLIP-194%3A+Introduce+the+JobResultStore
> Fabric8FlinkKubeClient.deleteConfigMap and deleteConfigMapsByLabels don't
> necessarily fail if the deletion didn't succeed
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-26695
> URL: https://issues.apache.org/jira/browse/FLINK-26695
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes, Runtime / Coordination
> Affects Versions: 1.15.0, 1.16.0
> Reporter: Matthias Pohl
> Priority: Major
>
> {{Fabric8FlinkKubeClient.deleteConfigMap}} and {{deleteConfigMapsByLabels}}
> do not evaluate the return value and, therefore, might miss an error during
> deletion.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
