Actually, its the other way around (thanks Sandy for catching this
error in my post). The presence of mapreduce.map|reduce.java.opts
overrides mapred.child.java.opts, not the other way round as I had
stated earlier (below).
On Wed, Dec 4, 2013 at 1:28 PM, Harsh J <[EMAIL PROTECTED]> wrote:
> Yes but the old property is yet to be entirely removed (removal of
> configs is graceful).
> These properties were introduced to provide more fine-tuned way to
> configure each type of task separately, but the older value continues
> to be accepted if present; the current behaviour is that if the MR
> runtime finds mapred.child.java.opts configured, it will override
> values of mapreduce.map|reduce.java.opts configs. To configure
> mapreduce.map|reduce.java.opts therefore, you should make sure you
> aren't passing mapred.child.java.opts (which is also no longer in the
> mapred-default.xml intentionally).
> On Wed, Dec 4, 2013 at 12:56 PM, Henry Hung <[EMAIL PROTECTED]> wrote:
>> I have a question.
>> Is it correct to say that in hadoop-2.2.0, the mapred-site.xml node
>> "mapred.child.java.opts” is replaced by two new node
>> “mapreduce.map.java.opts” and “mapreduce.reduce.java.opts”?
>> Best regards,
>> The privileged confidential information contained in this email is intended
>> for use only by the addressees as indicated by the original sender of this
>> email. If you are not the addressee indicated in this email or are not
>> responsible for delivery of the email to such a person, please kindly reply
>> to the sender indicating this fact and delete all copies of it from your
>> computer and network server immediately. Your cooperation is highly
>> appreciated. It is advised that any unauthorized use of confidential
>> information of Winbond is strictly prohibited; and any information in this
>> email irrelevant to the official business of Winbond shall be deemed as
>> neither given nor endorsed by Winbond.
> Harsh J