[
https://issues.apache.org/jira/browse/FLUME-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal resolved FLUME-237.
----------------------------------
Resolution: Won't Fix
Fix Version/s: v0.9.5
Won't fix. 0.X branch not maintained anymore
> documentation should describe flume installation issues - in particular
> specifying JVM heap sizes
> -------------------------------------------------------------------------------------------------
>
> Key: FLUME-237
> URL: https://issues.apache.org/jira/browse/FLUME-237
> Project: Flume
> Issue Type: Improvement
> Components: Docs
> Affects Versions: v0.9.0, v0.9.1
> Reporter: Patrick Hunt
> Fix For: v0.9.5
>
>
> I've updated the faq with some basic detail:
> "Why is Flume running out of memory?"
> http://github.com/cloudera/flume/wiki/FAQ
> however the flume documentation (man page?) should provide this detail.
> Probably it should include other aspects of setting up flume, gotchas etc...
> -------FAQ entry -------------
> Ensure that you have provided the jvm with sufficient heap space. By default
> Flume starts the jvm with it's default heap allocation, which differs
> depending on the jvm version, the host type (os, 32/64 bit, etc...), total
> host memory available, as well as other issues.
> The environment variable UOPTS can be used to pass additional jvm parameters
> when running Flume. e.g.
> $ UOPTS="-Xms1g -Xmx2g" bin/flume node
> which starts a flume node with an initial heap of one gig and a max heap of
> two gig. See "java -h" or "java -X" for more details on available jvm options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
