[
https://issues.apache.org/jira/browse/FLINK-27303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528594#comment-17528594
]
Yang Wang commented on FLINK-27303:
-----------------------------------
It seems we need to do the clean up manually in guava. I also find that we are
creating unnecessary pod template files in observer when upgrading a
FlinkDeployment. The root cause is that {{.lastReconciledSpec.job.state}} is
suspended.
Take it easy. This is not an urgent issue.
> Flink Operator will create a large amount of temp log config files
> ------------------------------------------------------------------
>
> Key: FLINK-27303
> URL: https://issues.apache.org/jira/browse/FLINK-27303
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.0.0
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Priority: Critical
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.0.0
>
>
> Now we use the configbuilder in multiple different places to generate the
> effective config including observer, reconciler, validator etc.
> The effective config gerenration logic also creates temporary log config
> files (if spec logConfiguration is set) which would lead to 3-4 files
> generated in every reconcile loop for a given job. These files are not
> cleaned up until the operator restarts leading to a large amount of files.
> I believe we should change the config generation logic and only apply the
> logconfig generation logic right before flink cluster submission as that is
> the only thing affected by it.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
