[jira] [Commented] (FLINK-13590) flink-on-yarn sometimes could create many little files that are xxx-taskmanager-conf.yaml

["Yang Wang (JIRA)" <ji...@apache.org>]

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

Yang Wang commented on FLINK-13590:
-----------------------------------

Hi [~shu_wenjun@qq.com]

Thanks for sharing this issue. I think it just because a file named \{uuid}-taskmanager-conf.yaml will be created for each task manager when launching a Yarn container. And it will only be cleaned up when the Yarn application finished. So the conf files will become more and more after task manager failover. It could be optimized to upload only one taskmanager-conf.yaml and override the different config options through task manager environment. Also the optimization could reduce the launch time for task manager.

Do you want to create a PR to fix this problem? Or i could take over this ticket.

> flink-on-yarn sometimes could create many little files that are xxx-taskmanager-conf.yaml
> -----------------------------------------------------------------------------------------
>
>                 Key: FLINK-13590
>                 URL: https://issues.apache.org/jira/browse/FLINK-13590
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN
>            Reporter: shuwenjun
>            Priority: Major
>         Attachments: taskmanager-conf-yaml.png
>
>
> Both of 1.7.2 and 1.8.0 are used, but they could create many little files.
>  These files are the configuration file of  taskmanager and when the flink session try to apply a new container, one of the files will be created. And I don't know why sometimes the flink session apply container again and again? Or when one container has lost, it could delete its taskmanager-conf.yaml 
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)