You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2011/06/12 07:15:51 UTC
[jira] [Commented] (MAPREDUCE-2547) TestDFSIO fails on a physical
cluster
[ https://issues.apache.org/jira/browse/MAPREDUCE-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048242#comment-13048242 ]
Konstantin Boudnik commented on MAPREDUCE-2547:
-----------------------------------------------
Turns out not a problem of the test. Rather the configuration was using an old way of configuring jobtracker address (mapred.job.tracker). Is this an intended behavior to simply ignore the old configuration parameter rather than issue a deprecation warning?
> TestDFSIO fails 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
> Assignee: 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