Chris Douglas commented on YARN-5621:

bq. this approach will not work in rollback scenario, as in that case no 
resources need to be localized - hence, no need to start the localizer 
processes. We only need to update the symlinks to old resources.

Sorry, I'm missing something. If the {{ContainerLocalizer}} supports a command 
to create symlinks to localized resources- a case that already exists for 
containers on the same node requesting the same resource- then how is that case 
distinguished from rollback? The container does need to start a 
{{ContainerLocalizer}} just to write some symlinks for the running container, 
which is inefficient. On the other hand, all symlinks for all containers from 
an application could be updated in the same invocation. When you say it does 
not work, are you noting the inefficiency of this flow, or is there a 
correctness problem?

> 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