hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Badger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6988) container-executor fails for docker when command length > 4096 B
Date Thu, 10 Aug 2017 21:19:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16122348#comment-16122348

Eric Badger commented on YARN-6988:

We should definitely increase the limit, but don't want to malloc the entire max amount of
memory that the system allows, since that would be a waste. A compromise could be to set the
arg length to the min of the system value and 128K. 

> 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
> {{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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message