Thanks for the responses. I am going to increase the worker.childopts heap size and that resolves the issue.
-- Kushan Maskey 817.403.7500 M. Miller & Associates <http://mmillerassociates.com/> [email protected] On Wed, Dec 10, 2014 at 9:30 AM, Huy Le Van <[email protected]> wrote: > Hi Kushan, > > This is an excellent tuning guide: https://gist.github.com/mrflip/5958028 > . You can find the suggested ‘worker.childopts’ to put into storm.yaml > there, which should eliminate the GC error. > > Best regards, > Huy, Le Van > > On Wednesday, Dec 10, 2014 at 3:25 p.m., Jens-U. Mozdzen <[email protected]>, > wrote: > >> Hi Kushan, >> >> Zitat von Kushan Maskey : >> >> > I am getting bunch of GC error as following. Where do I specify or >> increase >> > the memory in the storm? >> > >> > java.lang.OutOfMemoryError: GC overhead limit exceeded at >> > java.lang.reflect.Method.copy(Method.java:151) at >> > java.lang.reflect.ReflectAccess.copyMethod(ReflectAccess.java:136) at >> > sun.reflect.ReflectionFactory.copyMethod(ReflectionFactory.java:300) at >> > java.lang.Class.copyMethods(Class.java:2852) at >> > java.lang.Class.getMethods(Class.java:1467) at >> > clojure.lang.Reflector.getMethods(Reflector.java:357) at >> > clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:296) at >> > clojure.tools.logging$eval1$fn__2.invoke(NO_SOURCE_FILE:0) at >> > clojure.tools.logging.impl$fn__39$G__17__46.invoke(impl.clj:16) at >> > backtype.storm.daemon.executor$fail_spout_msg.invoke(executor.clj:369) >> at >> >> these seem to be errors from a worker log - you can update the >> supervisor's configuration (in storm.yaml) to specify worker options, >> i.e. setting memory size and/or garbage collector tuning options. >> >> Regards, >> [email protected]> > >
