Hi all,

We have Flink jobs run on batch mode and get the job status via JobHandler.
onJobExecuted
<https://ci.apache.org/projects/flink/flink-docs-master/api/java/org/apache/flink/core/execution/JobListener.html#onJobExecuted-org.apache.flink.api.common.JobExecutionResult-java.lang.Throwable->
()[1].

Base on the thread[2], we expected the Configmaps will be cleaned up after
execution successfully.

But we found some Configmaps not be cleanup after job success. On the other
hand, the Configmaps contents and the labels are removed.

Here is one of the Configmaps.

```
apiVersion: v1
kind: ConfigMap
metadata:
  name: match-6370b6ab-de17-4c93-940e-0ce06d05a7b8-resourcemanager-leader
  namespace: app-flink
  selfLink: >-

/api/v1/namespaces/app-flink/configmaps/match-6370b6ab-de17-4c93-940e-0ce06d05a7b8-resourcemanager-leader
  uid: 80c79c87-d6e2-4641-b13f-338c3d3154b0
  resourceVersion: '578806788'
  creationTimestamp: '2021-10-21T17:06:48Z'
  annotations:
    control-plane.alpha.kubernetes.io/leader: >-

{"holderIdentity":"3da40a4a-0346-49e5-8d18-b04a68239bf3","leaseDuration":15.000000000,"acquireTime":"2021-10-21T17:06:48.092264Z","renewTime":"2021-10-21T17:06:48.092264Z","leaderTransitions":0}
  managedFields:
    - manager: okhttp
      operation: Update
      apiVersion: v1
      time: '2021-10-21T17:06:48Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:annotations':
            .: {}
            'f:control-plane.alpha.kubernetes.io/leader': {}
data: {}
```


Our Flink apps run on ver. 1.14.0.
Thanks!

BR,
Oscar


Reference:
[1] JobListener (Flink : 1.15-SNAPSHOT API) (apache.org)
<https://ci.apache.org/projects/flink/flink-docs-master/api/java/org/apache/flink/core/execution/JobListener.html>
[2]
https://lists.apache.org/list.html?user@flink.apache.org:lte=1M:High%20availability%20data%20clean%20up%20

Reply via email to