Thanks, Mingjie. The solution for us was to increase the JOPTS value in /usr/lib/flume/bin/flume.
On 10/11/11 3:07 AM, "Mingjie Lai" <[email protected]> wrote: >You can try to use ``jps -v'' to see whether the jvm options applied. > >In bin/flume, I also saw that the watch dog also use JOPTS, so it will >also allocate the same amount of heap besides flume master/nodes. Should >be a bug. > > >On 10/10/2011 11:12 AM, Hammerman, Joseph wrote: >> Hi Flume-users list. >> >> We seem to only be able to allocate 2Gb of memory to the JVM on our >>x86_64 >> bit machine - does anyone know if there is a a system wide setting for >> this? We attempted to force the process to allocate 3Gb for itself using >> JOPTS in /usr/lib/flume/bin/flume, but it did not help: >> >> JOPTS="-Xms3g -Xmx3g" >> >> We are seeing this in the flume master output file: >> >> Exception in thread "pool-1-thread-15" java.lang.OutOfMemoryError: Java >> heap space >> Exception in thread "pool-1-thread-10" java.lang.OutOfMemoryError: Java >> heap space >> >> I provide more information as needed. >> >> >> Thanks >> Joe >> >>
