[jira] [Commented] (FLINK-14582) Do not upload {uuid}-taskmanager-conf.yaml for each task manager container

["Till Rohrmann (Jira)" <ji...@apache.org>]

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

Till Rohrmann commented on FLINK-14582:
---------------------------------------

This could mitigate the problem a bit. But wouldn't it be easier to first call {{removeContainerRequest}} for all reported {{containers}} in {{YarnResourceManager#onContainersAllocated}} before starting the {{TaskExecutors}}? Then it would not matter how long the file upload would last.

> Do not upload {uuid}-taskmanager-conf.yaml for each task manager container
> --------------------------------------------------------------------------
>
>                 Key: FLINK-14582
>                 URL: https://issues.apache.org/jira/browse/FLINK-14582
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / YARN
>    Affects Versions: 1.10.0, 1.9.1
>            Reporter: Yang Wang
>            Priority: Minor
>
> Currently when we {{createTaskExecutorLaunchContext}}, a new task manager conf will be created and uploaded to hdfs. The time cost is unnecessary and could be reduced by using java options of task manager main class instead.
> By reducing the time of launch container in {{onContainersAllocated}}, we could avoid allocating excess containers as much as possible.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)