[
https://issues.apache.org/jira/browse/YARN-8672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677453#comment-16677453
]
Chandni Singh commented on YARN-8672:
-------------------------------------
[~eyang] Thanks. I see that in the container-executor.c {{initialize_app}}
function line 1313 - 1325 the token file is copied to the working directory but
in this case (unlike Default Container executor), the original token file name
is retained.
There are 2 ways to address this:
1. Change container executor.c to copy the token file but not retain the
original name. Similar to Default Container executor, it changes the name to
<contianerid>.tokens
2. Change ContainerLocalizer to accept the token file name as an argument.
I think 2nd option is better but it will be a backward compatible change for
ContainerLocalizer because token file name will be a mandatory argument and
ContainerLocalizer seems to be a standalone program.
Please let me know your thoughts
> TestContainerManager#testLocalingResourceWhileContainerRunning occasionally
> times out
> -------------------------------------------------------------------------------------
>
> Key: YARN-8672
> URL: https://issues.apache.org/jira/browse/YARN-8672
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.2.0
> Reporter: Jason Lowe
> Assignee: Chandni Singh
> Priority: Major
> Attachments: YARN-8672.001.patch, YARN-8672.002.patch,
> YARN-8672.003.patch, YARN-8672.004.patch, YARN-8672.005.patch
>
>
> Precommit builds have been failing in
> TestContainerManager#testLocalingResourceWhileContainerRunning. I have been
> able to reproduce the problem without any patch applied if I run the test
> enough times. It looks like something is removing container tokens from the
> nmPrivate area just as a new localizer starts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
