[
https://issues.apache.org/jira/browse/OOZIE-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453293#comment-13453293
]
Harsh J commented on OOZIE-986:
-------------------------------
bq. which it seems like java does if I don't use "-Xmx".
Java JVMs will use a percentage (15-25% IIRC, implementation/version specific)
of the global RAM if a max heap size limit is unset. So it may easily consume
more than 1 GB.
Since the actual issue is fixed, can you re-edit the title and submit a patch
for ensuring the consistency in naming?
> 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
