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] Commented: (MAPREDUCE-40) Memory management variables need a backwards compatibility option after HADOOP-5881
Date Fri, 17 Jul 2009 07:42:14 GMT

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

Hemanth Yamijala commented on MAPREDUCE-40:

I found a couple of places where warning messages are not being printed while using the old
values. Examples are JobTracker.initializeTaskMemoryRelatedConfig, CapacityTaskScheduler.initializeMemoryRelatedConf,
the deprecated JobConf APIs and the new APIs when we return the old values. Can you please
change this and upload a new patch ?

> Memory management variables need a backwards compatibility option after HADOOP-5881
> -----------------------------------------------------------------------------------
>                 Key: MAPREDUCE-40
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-40
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Hemanth Yamijala
>            Assignee: rahul k singh
>            Priority: Blocker
>         Attachments: hadoop-5919-1.patch, hadoop-5919-10.patch, hadoop-5919-11.patch,
hadoop-5919-12-20.patch, hadoop-5919-12.patch, hadoop-5919-13-20.patch, hadoop-5919-13.patch,
hadoop-5919-2.patch, hadoop-5919-3.patch, hadoop-5919-4.patch, hadoop-5919-5.patch, hadoop-5919-6.patch,
hadoop-5919-7.patch, hadoop-5919-8.patch, hadoop-5919-9.patch
> HADOOP-5881 modified variables related to memory management without looking at the backwards
compatibility angle. This JIRA is to adress the gap. Marking it a blocker for 0.20.1

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

View raw message