AnsweredAssumed Answered

Why is mapred.map.child.java.opts deprecated?

Question asked by mnaseef on Jan 25, 2012
Latest reply on Jan 25, 2012 by mnaseef
Hi, we noticed recently that a few options in the mapred-site.xml are tagged (via XML comment) as being deprecated, specifically mapred.map.child.java.opts, mapred.map.child.ulimit, and mapred.map.child.env and I am wondering why that is. We used to use the first two to configure memory, but found that removing them actually works better now.

This is not a big concern for us at the moment, but we do sometimes use these to experiment with features such as the AggressiveOpts feature, and I can see us possibly wanting to use opts and env in similar ways in the future. Am I interpreting the comments in mapred-site.xml correctly in that the reduce versions of these parameters are not deprecated? Is it possible to set these parameters without breaking map-reduce on MapR, and, if so, will it continue to be possible going forward?

Outcomes