[
https://issues.apache.org/jira/browse/MAPREDUCE-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745318#action_12745318
]
Hemanth Yamijala commented on MAPREDUCE-832:
--------------------------------------------
bq. -1 tests included. The patch doesn't appear to include any new or modified
tests.
The patch is adding a debug log message which is hard to write a unit test for.
Our QE team has manually verified the patch by running tests on a cluster with
old memory configuration and verifying that the number of WARN messages has
come down drastically. Also, the scenario in MAPREDUCE-833 has been tested and
found fixed.
bq. -1 core tests. The patch failed core unit tests.
org.apache.hadoop.mapred.TestRecoveryManager.testRestartCount's failure is
independent of this patch. It happens with trunk and is being tracked in
MAPREDUCE-880
bq. -1 contrib tests. The patch failed contrib unit tests.
The streaming test failures have been happening for a while on hudson alone.
They pass locally.
On this basis, I am going to commit the patch to trunk and an equivalent patch
to branch 20.
> 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
> Assignee: rahul k 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.
