hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj K (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4159) Job is running in Uber mode after setting "mapreduce.job.ubertask.maxreduces" to zero
Date Wed, 18 Apr 2012 12:59:44 GMT

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

Devaraj K commented on MAPREDUCE-4159:
--------------------------------------

It is not considering the value of 'mapreduce.job.ubertask.maxreduces' while making the job
uber mode decision.
                
> Job is running in Uber mode after setting "mapreduce.job.ubertask.maxreduces" to zero
> -------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4159
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4159
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 2.0.0
>            Reporter: Nishan Shetty
>
> 1.Configure "mapreduce.job.ubertask.enable" to true
> 2.Configure "mapreduce.job.ubertask.maxreduces" to 0(zero)
> 3.Run job such that it has one reducer(more than "mapreduce.job.ubertask.maxreduces"
value) 
> Observe that job is running in Uber mode instead of normal mode(non uber mode)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message