Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.23.9, 2.2.0
-
None
-
Incompatible change
-
Prior to this change, distcp had hard-coded values for memory usage. Now distcp will honor memory settings in a way compatible with the rest of MapReduce.
Description
When a DistCp job is run through Oozie (through a Java action that launches DistCp), one sees that mapred.child.java.opts as set from the caller is honoured by DistCp. But, DistCp doesn't seem to honour any overrides for configs mapreduce.[map,reduce].memory.mb.
Problem has been identified. I'll post a patch shortly.