Jian He commented on YARN-5621:

My original thought is to create the symlinks right after localization 
completes. Then I realized for existing resource, no localizer process is 
created, and, yeah, I feel it's inefficient to start a localizer process to 
only create symlinks.. 
Not sure I understand below right..
bq. a case that already exists for containers on the same node requesting the 
same resource
Do you mean this is an existing implemented functionality or this is an 
existing use-case? I think the former is not true.   The latter is true which 
is currently done by the container_launch script to create symlinks

> Support LinuxContainerExecutor to create symlinks for continuously localized 
> resources
> --------------------------------------------------------------------------------------
>                 Key: YARN-5621
>                 URL: https://issues.apache.org/jira/browse/YARN-5621
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Jian He
>            Assignee: Jian He
>         Attachments: YARN-5621.1.patch, YARN-5621.2.patch, YARN-5621.3.patch, 
> YARN-5621.4.patch, YARN-5621.5.patch
> When new resources are localized, new symlink needs to be created for the 
> localized resource. This is the change for the LinuxContainerExecutor to 
> create the symlinks.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to