hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chuan Liu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5349) TestClusterMapReduceTestCase and TestJobName fail on Windows in branch-2
Date Mon, 24 Jun 2013 17:32:20 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chuan Liu updated MAPREDUCE-5349:

    Attachment: MAPREDUCE-5349-branch-2.patch

Attach a patch. The fix is simple: changing MiniMRCluster to use simple name as the identifier;
making it the same as trunk code.
> TestClusterMapReduceTestCase and TestJobName fail on Windows in branch-2
> ------------------------------------------------------------------------
>                 Key: MAPREDUCE-5349
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5349
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.1.0-beta
>            Reporter: Chuan Liu
>            Assignee: Chuan Liu
>            Priority: Minor
>         Attachments: MAPREDUCE-5349-branch-2.patch
> The two unit tests fails due to MiniMRCluster use test class fullname in branch-2, instead
of simple name as in trunk, to construct the MiniMRCluster identifier. Full name in the identifier
almost always leads to a command script path with length larger than 260 characters which
will generate an exception {{DefaultContainerExecutor.launchContainer()}} when launching the
container script.
> The exception looks like the follows:
> {noformat}
> 2013-06-24 09:45:03,060 WARN  [ContainersLauncher #0] launcher.ContainerLaunch (ContainerLaunch.java:call(262))
- Failed to launch container.
> java.io.IOException: Cannot launch container using script at path C:/Users/chuanliu/AppData/Local/Temp/1/1372092295656/org.apache.hadoop.mapred.ClusterMapReduceTestCaseConfigurableMiniMRCluster_1106798455-localDir-nm-0_1/usercache/chuanliu/appcache/application_1372092193505_0001/container_1372092193505_0001_01_000001/default_container_executor.cmd,
because it exceeds the maximum supported path length of 260 characters.  Consider configuring
shorter directories in yarn.nodemanager.local-dirs.
> 	at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:159)
> 	at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:257)
> 	at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:1)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)
> {noformat}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message