[
https://issues.apache.org/jira/browse/YARN-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491452#comment-15491452
]
Chris Douglas commented on YARN-5621:
-------------------------------------
bq. This may be a viable approach, we need to change the localizer heartbeat to
send the symlink path.
The heartbeat already carries a payload with commands to the localizer.
Including actions to symlink resources already fetched isn't that dire a change
to either the ContainerLocalizer or the resource state machine, is it? The
transition needs to send a LINK request to all localizers that were waiting in
case the download failed.
bq. But if we want to create all symlinks in one go, this approach will not
work.
This isn't going to be a transaction on the FS regardless, but can you explain
this requirement? If symlink-on-download is disqualifying, then the container
could still coordinate grouped symlinks by grouping LINK requests to a
localizer. It rearranges the event flows awkwardly, but it's supportable...
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
