[
https://issues.apache.org/jira/browse/MAPREDUCE-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349233#comment-14349233
]
Mithun Radhakrishnan commented on MAPREDUCE-5653:
-------------------------------------------------
Hey, [~rdsr]. (Long time! :]). Hello, [~aw]. Apologies for the unreasonably
delayed response.
Thank you both for addressing this. I agree. Removing those properties from the
default.xml does solve the immediate problem.
It's a different matter that the initialization path is still incorrect
(because of how/when default.xml is loaded). This might not be of consequence.
Should that change later, we'll tackle that in a separate JIRA.
Cheers.
> DistCp does not honour config-overrides for mapreduce.[map,reduce].memory.mb
> ----------------------------------------------------------------------------
>
> Key: MAPREDUCE-5653
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5653
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: distcp
> Affects Versions: trunk, 0.23.9, 2.2.0
> Reporter: Mithun Radhakrishnan
> Assignee: Ratandeep Ratti
> Fix For: 3.0.0
>
> Attachments: MAPREDUCE-5653.branch-0.23.patch,
> MAPREDUCE-5653.branch-2.patch, MAPREDUCE-5653.trunk.2.patch,
> MAPREDUCE-5653.trunk.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)