[
https://issues.apache.org/jira/browse/FLINK-24894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443643#comment-17443643
]
Yangze Guo commented on FLINK-24894:
------------------------------------
[~long jiang] As recorded in [1], if you manually delete the deployment, HA
related Configmaps will be retained. Please use `./bin/flink cancel` instead[2].
[1]
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/#high-availability-data-clean-up
[2]
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#deployment-modes
> Flink on k8s, open the HA mode based on KubernetesHaServicesFactory ，When I
> deleted the job, the config map created under the HA mechanism was not
> deleted.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-24894
> URL: https://issues.apache.org/jira/browse/FLINK-24894
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Environment: 1.13.2
> Reporter: john
> Priority: Major
>
> Flink on k8s, open the HA mode based on KubernetesHaServicesFactory. When I
> deleted the job, the config map created under the HA mechanism was not
> deleted. This leads to a problem: if my last concurrency was 100, changing to
> 40 this time will not take effect. This can be understood because jobgraph
> recovered from high-availability.storageDir and ignored the client's.
> My question is: When deleting a job, the config map created under the HA
> mechanism is not deleted. Is this the default mechanism of HA, or is it a bug?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
