[jira] [Updated] (FLINK-27303) Flink Operator will create a large amount of temp log config files

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-27303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-27303:
-----------------------------------
    Labels: pull-request-available  (was: )

> 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)