You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Alexander Lorenz-Alten (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/07 12:02:58 UTC

[jira] [Resolved] (FLUME-237) documentation should describe flume installation issues - in particular specifying JVM heap sizes

     [ https://issues.apache.org/jira/browse/FLUME-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lorenz-Alten resolved FLUME-237.
------------------------------------------

    Resolution: Won't Fix
    
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira