[
https://issues.apache.org/jira/browse/YARN-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444951#comment-16444951
]
Eric Yang commented on YARN-8064:
---------------------------------
{code}
2018-04-19 22:32:01,480 WARN
org.apache.hadoop.yarn.server.nodemanager.containermanager.linux.runtime.docker.DockerClient:
Unable to write docker command to
/tmp/hadoop-yarn/nm-local-dir/nmPrivate/application_1524177007026_0001/container_1524177007026_0001_01_000002
{code}
It looks like the container directory creation might have race condition with
cmd file generation. I see this error logged when container directory is
empty. In my test case, there is nothing to localize, hence container
directory doesn't exist, and resulting in cmd file generation fails.
> Docker ".cmd" files should not be put in hadoop.tmp.dir
> -------------------------------------------------------
>
> Key: YARN-8064
> URL: https://issues.apache.org/jira/browse/YARN-8064
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Eric Badger
> Assignee: Eric Badger
> Priority: Critical
> Attachments: YARN-8064.001.patch, YARN-8064.002.patch,
> YARN-8064.003.patch, YARN-8064.004.patch, YARN-8064.005.patch,
> YARN-8064.006.patch, YARN-8064.007.patch, YARN-8064.008.patch
>
>
> Currently all of the docker command files are being put into
> {{hadoop.tmp.dir}}, which doesn't get cleaned up. So, eventually all of the
> inodes will fill up and no more tasks will be able to run
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
