Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 1 Nov 2016 16:46:58 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12922292.1450254930000.145824.1478018818416@Atlassian.JIRA>
In-Reply-To: <JIRA.12922292.1450254930000@Atlassian.JIRA>
References: <JIRA.12922292.1450254930000@Atlassian.JIRA> <JIRA.12922292.1450254930498@arcas>
Subject: [jira] [Commented] (YARN-4463) Container launch failure when
 yarn.nodemanager.log-dirs directory path contains space
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 01 Nov 2016 16:47:00 -0000


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

Varun Saxena commented on YARN-4463:
------------------------------------

[~bibinchundatt], thanks for raising this issue. The issue is because command line arguments have to be quoted if they carry spaces. This issue would not only be with log dirs but local dirs as well. And the issue IIUC may not only be restricted to DCE but LCE as well.

This can be resolved by putting wherever log dirs and local dirs are used within single quotes(') and double quotes(") when we create the different scripts such as launch_container.sh
Please note we already do this when we export environment variables in the script. But some places it has not been handled.
I was for instance able to fix the issue reported in the JIRA and run the job successfully after making changes in ContainerLaunch#call (by putting a single quote around the command line java property values where LOG dir had to be expanded).

You can discuss with me offline and then we can work towards a more comprehensive fix for the issue.

> Container launch failure when yarn.nodemanager.log-dirs directory path contains space
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-4463
>                 URL: https://issues.apache.org/jira/browse/YARN-4463
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>
> If the container log directory path contains space container-launch fails
> Even with DEBUG logs are enabled only log able to get is 
> {noformat}
> Container id: container_e32_1450233925719_0009_01_000022
> Exit code: 1
> Stack trace: ExitCodeException exitCode=1:
>         at org.apache.hadoop.util.Shell.runCommand(Shell.java:912)
>         at org.apache.hadoop.util.Shell.run(Shell.java:823)
>         at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:1102)
>         at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:225)
>         at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:304)
>         at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:84)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>         at java.lang.Thread.run(Thread.java:745)
> {noformat}
> We can support container-launch to support nmlog directory path with space.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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