[
https://issues.apache.org/jira/browse/FLINK-13590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901802#comment-16901802
]
shuwenjun commented on FLINK-13590:
-----------------------------------
Hi Yang，
You are right, it's right that the files are created when launching a new yarn
container. And it is better optimized to override taskmanager-conf.yaml. Now,
it could cause a more serious problem, that it will produce hundreds of
thousands of small files, because the RM keep retrying to apply for
taskmanager(container) when the source is enough. And the RM always don't get
some new correct taskmanagers.
Thank you for your comment.
> 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)
