hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-832) Too many WARN messages about deprecated memorty config variables in JobTacker log
Date Wed, 19 Aug 2009 04:53:14 GMT

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

Hemanth Yamijala updated MAPREDUCE-832:
---------------------------------------

    Attachment: mapreduce-832.patch

Attached a new patch that works for trunk. It is the same as what Rahul uploaded, except I
modified the method checkAndWarnDeprecation to not require a Configuration instance. Instead,
it uses the current object's values itself. Running this through Hudson

> Too many WARN messages about deprecated memorty config variables in JobTacker log
> ---------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-832
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-832
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.20.1
>            Reporter: Karam Singh
>         Attachments: mapreduce-832-20.patch, mapreduce-832.patch
>
>
> When user submit a mapred job using old memory config vairiable (mapred.task.maxmem)
followinig message too many times in JobTracker logs -:
> [
> WARN org.apache.hadoop.mapred.JobConf: The variable mapred.task.maxvmem is no longer
used instead use  mapred.job.map.memory.mb and mapred.job.reduce.memory.mb
> ]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message