You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2021/06/02 09:28:00 UTC
[jira] [Commented] (FLINK-22841) how to update configuration of the
native kubernetes deployment model flink cluster?
[ https://issues.apache.org/jira/browse/FLINK-22841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355602#comment-17355602 ]
Yang Wang commented on FLINK-22841:
-----------------------------------
If you want to update the Flink configuration and expect the JobManager restarted with new configuration automatically, as well as the TaskManager, then I have to say Flink could not. Because it is not the responsibility of Flink. Instead, the deployer tools should support this.
Currently, you could achieve by some manual operations.
* Use {{kubectl edit cm flink-config-CLUSTER_ID}} to edit the flink configuration
* Kill the JobManager pod and all the TaskManager pods
* A new JobManager will be launched by K8s. And Flink will allocate new TaskManager pods to run jobs.
> how to update configuration of the native kubernetes deployment model flink cluster?
> ------------------------------------------------------------------------------------
>
> Key: FLINK-22841
> URL: https://issues.apache.org/jira/browse/FLINK-22841
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Affects Versions: 1.13.0
> Environment: flink 1.30
> k8s 1.16.9
> docker image flink:1.13.0
> Reporter: lukehua
> Priority: Major
>
> when i deploy flink with the native session model ,how can i update the configuration of the flink cluster? i can use the script kubernetes-session.sh to change the flink-conf.yaml, but the deployment of jobmanager does not restart the pod automatically，and the taskmanager pod does not restart one by one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)