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 2022/04/22 08:06:00 UTC

[jira] [Comment Edited] (FLINK-27345) operator does not update related resource when flinkConfiguration, logConfiguration are updated.

    [ https://issues.apache.org/jira/browse/FLINK-27345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526255#comment-17526255 ] 

Yang Wang edited comment on FLINK-27345 at 4/22/22 8:05 AM:
------------------------------------------------------------

I think updating the flinkConfiguration or logConfiguration in CR could trigger the redeploy. Could you please check the operator logs for more information?


was (Author: fly_in_gis):
I think updating the flinkConfiguration or logConfiguration in CR could trigger the redeploy. Could you please check the operator logs for more information.

> operator does not update related resource when flinkConfiguration, logConfiguration are updated.
> ------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-27345
>                 URL: https://issues.apache.org/jira/browse/FLINK-27345
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: ChangZhuo Chen (陳昌倬)
>            Priority: Major
>
> The CRD FlinkDeployment does not update running jobmanager/taskmanager when flinkConfiguration or logConfiguration are updated. We need to recreate FlinkDeployment to make it works.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)