[ https://issues.apache.org/jira/browse/YARN-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131325#comment-16131325 ]
Hudson commented on YARN-6988: ------------------------------ SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #12205 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/12205/]) YARN-6988. container-executor fails for docker when command length > (jlowe: rev ab1a8ae85f8c61304a0f437cdc61cc5aeda36a4b) * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/util.h * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/container-executor.c > container-executor fails for docker when command length > 4096 B > ---------------------------------------------------------------- > > Key: YARN-6988 > URL: https://issues.apache.org/jira/browse/YARN-6988 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn > Reporter: Eric Badger > Assignee: Eric Badger > Fix For: 3.0.0-beta1 > > Attachments: YARN-6988.001.patch, YARN-6988.002.patch > > > {{run_docker}} and {{launch_docker_container_as_user}} allocate their command > arrays using EXECUTOR_PATH_MAX, which is hardcoded to 4096 in > configuration.h. Because of this, the full docker command can only be 4096 > characters. If it is longer, it will be truncated and the command will fail > with a parsing error. Because of the bind-mounting of volumes, the arguments > to the docker command can quickly get large. For example, I passed the 4096 > limit with an 11 disk node. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org