[
https://issues.apache.org/jira/browse/SAMZA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815797#comment-13815797
]
Rekha Joshi commented on SAMZA-76:
----------------------------------
export JAVA_OPTS="-Xmx1024m".
Attached patch.
However unsure if this is ideal for 2 reasons:
1.JAVA_OPTS(or _JAVA_OPTIONS) would cater to all of jvm/java applications and
using that as default?
2.Logic is to use other env var default max heap size when SMAZA_OPTS is not
set/defined.But JAVA_OPTS max heap size can be set to greater than in
SAMZA_OPTS for some use-cases.Not ideal.
Which might mean we may consider to set our own SAMZA_DEFAULTS env var, but
that is catch-22.If SAMZA_OPTS can be undefined, so can the SAMZA_DEFAULTS.
I am not able to load https://github.com/linkedin/hello-samza/issues/4
> Improve default memory settings for samza tasks
> -----------------------------------------------
>
> Key: SAMZA-76
> URL: https://issues.apache.org/jira/browse/SAMZA-76
> Project: Samza
> Issue Type: Improvement
> Reporter: Jakob Homan
> Priority: Minor
> Attachments: run_class.sh
>
>
> The {{run-class.sh}} script hardcodes the xmx setting for the launched class
> at 160M. This is generally too low, and should be bumped up, but should also
> be specified in a more overridable-friendly way via an environmental variable.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
