[
https://issues.apache.org/jira/browse/MAPREDUCE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983575#action_12983575
]
Todd Lipcon commented on MAPREDUCE-1085:
----------------------------------------
We already return null from getVMSetupCmd in other cases - take a look at
Shell.getUlimitMemoryCommand and you'll see that we return null there for
Windows as is.
Not sure which code you're refering to above with setupCmds.add(setup). It's
not in trunk.
The flow is: launchJvmAndWait -> JvmManager.constructJvmEnv -> JvmEnv data
structure -> TaskLog.buildCommandLine where you see the null check:
{code}
if (setup != null && setup.size() > 0) {
mergedCmd.append(addCommand(setup, false));
mergedCmd.append(";");
}
{code}
> For tasks, "ulimit -v -1" is being run when user doesn't specify
> mapred.child.ulimit
> ------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1085
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1085
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Ravi Gummadi
> Assignee: Todd Lipcon
> Priority: Minor
> Attachments: mapreduce-1085.txt
>
>
> For tasks, "ulimit -v -1" is being run when user doesn't specify
> mapred.child.ulimit. Taking -1 as default value and using it in building the
> command is not right.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
