[
https://issues.apache.org/jira/browse/MAPREDUCE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727915#action_12727915
]
Hemanth Yamijala commented on MAPREDUCE-40:
-------------------------------------------
In an offline discussion, the following two comments came up:
- The test cases seem to test every high memory test case in two modes - with
the old variables and with the new variables. I think that's overkill and is
making the test cases hard to maintain over a long run.
- Some memory related variables (related to physical memory configuration) are
removed in a backwards incompatible manner. If they are configured in the conf
files we should print a warning message to the users. I don't know if this is
already done. If yes, please ignore this.
> 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-2.patch,
> hadoop-5919-3.patch, hadoop-5919-4.patch, hadoop-5919-5.patch,
> hadoop-5919-6.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.
