[jira] [Resolved] (MAPREDUCE-5318) Ampersand in JSPUtil.java is not escaped
[ https://issues.apache.org/jira/browse/MAPREDUCE-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bohou Li resolved MAPREDUCE-5318. - Resolution: Fixed Ampersand in JSPUtil.java is not escaped Key: MAPREDUCE-5318 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5318 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobtracker Affects Versions: 1.1.2 Reporter: Bohou Li Assignee: Bohou Li Priority: Minor Attachments: JSPUtil.class, MAPREDUCE-5318-br1.patch The malformed urls cause hue crash. The malformed urls are caused by the unescaped ampersand . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: mapred.child.ulimit in MR2
Thanks Bobby, I filed MAPREDUCE-5338 for it. -Sandy On Wed, Jun 19, 2013 at 8:16 AM, Robert Evans ev...@yahoo-inc.com wrote: Sandy, I think it was something that was missed in the port to YARN and the dead code was cleaned up as part of HADOOP-8288. If you have a use case for it or are worried about backwards compatibility we can add it back in. It is not that hard, all it did was add 'ulimt -v number' to the shell script that launched the task, except on windows. --Bobby On 6/18/13 3:56 PM, Sandy Ryza sandy.r...@cloudera.com wrote: Hi yarn-dev/mapreduce-dev, Is there a reason that mapred.child.ulimit no longer has an effect in MR2? Should it be added back in? thanks for any help, -Sandy
[jira] [Created] (MAPREDUCE-5338) Bring back mapred.child.ulimit
Sandy Ryza created MAPREDUCE-5338: - Summary: Bring back mapred.child.ulimit Key: MAPREDUCE-5338 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5338 Project: Hadoop Map/Reduce Issue Type: Improvement Affects Versions: 2.0.5-alpha Reporter: Sandy Ryza In MR1, a ulimit could be set for MapReduce child processes. For parity, this would be good to have in MR2 as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
