[
https://issues.apache.org/jira/browse/OOZIE-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451380#comment-13451380
]
Harsh J commented on OOZIE-986:
-------------------------------
[~tucu00] - He's speaking of bin/oozie OozieCLI client.
[~stevenwillis] - We already provide an env-var allowance via JAVA_PROPERTIES.
So for example you may do, if you need higher heap for the OozieCLI:
$ {{JAVA_PROPERTIES=-Xmx1024m oozie <args>}}
Does this work for you, or would you still like it to be renamed?
The OozieCLI doesn't do too much work other than listing things, or sending
simple config sets to server, so I've yet to see a need to raise heap for it.
What scenario or command lead to its OOME for you btw?
> Oozie shell script should allow for setting of java options
> -----------------------------------------------------------
>
> Key: OOZIE-986
> URL: https://issues.apache.org/jira/browse/OOZIE-986
> Project: Oozie
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 3.1.3, 3.2.0
> Environment: RHEL 6.0
> Reporter: Steven Willis
> Labels: java, options, shellscript
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> All the hadoop shell scripts (hadoop, hdfs, mapred, yarn) allow the setting
> of HADOOP_CLIENT_OPTS to pass custom options to java. I think the oozie shell
> script should allow the same through OOZIE_CLIENT_OPTS and similarly respect
> JAVA_HEAP_MAX like the hadoop shell scripts.
--
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
