hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4695) Fix LocalRunner on trunk after MAPREDUCE-3223 broke it
Date Mon, 01 Oct 2012 17:03:07 GMT

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

Harsh J updated MAPREDUCE-4695:

    Attachment: MAPREDUCE-4695.patch

bq. The patch looks good. I don't think that ClientServiceDelegate.java needs to be changed
at all.

Thats my dummy change to trigger tests in jobclient (tests reside there, while default xml
is in core, a problem we've yet to fix, will follow up on this afterwards). It won't go into
the final patch.

bq. It would also be nice to add in a test so that changes like this don't break it again
in the future, but I am not sure how easy that would be so I am OK without it.

If we moved all tests to their right module we wouldn't have this issue (i.e. we won't miss
it in pre commit builds).

Thanks Robert, I'll commit this in (new patch minus jobclient package change).
> Fix LocalRunner on trunk after MAPREDUCE-3223 broke it
> ------------------------------------------------------
>                 Key: MAPREDUCE-4695
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4695
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Blocker
>         Attachments: MAPREDUCE-4695.patch, MAPREDUCE-4695.patch
> MAPREDUCE-3223 removed mapreduce.cluster.local.dir property from mapred-default.xml (since
NM local dirs are now used) but failed to counter that LocalJobRunner, etc. still use it.
> {code}
> mr-3223.txt:-  <name>mapreduce.cluster.local.dir</name>
> mr-3223.txt--  <value>${hadoop.tmp.dir}/mapred/local</value>
> {code}
> All local job tests have been failing since then.
> This JIRA is to reintroduce it or provide an equivalent new config for fixing it.

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