Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 31 May 2011 01:15:47 +0000 (UTC)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1988483994.54762.1306804547356.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <559040584.54755.1306804007383.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-2547) TestDFSIO failes on a physical
 cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Boudnik commented on MAPREDUCE-2547:
-----------------------------------------------

You'll see the following error message
{noformat}
11/05/31 01:13:57 INFO util.NativeCodeLoader: Loaded the native-hadoop library
11/05/31 01:13:57 INFO mapreduce.JobSubmitter: Cleaning up the staging area file:/user/cos1445850318/.staging/job_local_0001
ENOENT: No such file or directory
{noformat}

If the same test is executed with {{-jt jobtracker:port}} command line argument everything works fine.

It would seem like a configuration problem unless this is the only test/example with doesn't work properly. Sleep jobs, Pi, randomwriter jobs are working just fine.

> TestDFSIO failes on a physical cluster
> --------------------------------------
>
>                 Key: MAPREDUCE-2547
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2547
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.22.0
>         Environment: Physical cluster based on 0.22-SNAPSHOT
>            Reporter: Konstantin Boudnik
>            Priority: Blocker
>
> An attempt to run TestDSFIO on cluster fails because TestDFSIO tries to run MR job with local runner. If JT is explicitly specified via {{-jt}} cmd. arg. then everything is working as expected.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira