Yes, this is the way to increase memory for storm. I would add one caveat: this is the per worker memory allocation. So one has to dimension the memory available in the machine and plan for *number of workers* accordingly, e.g. a server with 64GB RAM will struggle if you start on it ten workers with -Xms10GB :)
On Fri, Jun 5, 2015 at 12:23 PM, Matthias J. Sax < [email protected]> wrote: > I would set the needed JVM arguments in storm.yaml file. This must be > done on every worker node. > > worker.childopts: "-Xmx4096m" > ( or maybe > supervisor.childopts: "-Xmx496m" ) > > -Matthias > > On 06/05/2015 05:11 PM, Prakash Ramesh Dayaramani wrote: > > Hi All, > > > > I am trying to deploy jar on storm cluster which loads > > volume of data at startup and stores it into memory. However, while > > deploying that jar itself its throwing outofmemory error. > > > > When I tried this option on local topology it was working fine. And it > > takes command line arguments of minmax settings java. (–Xmx4096m) > > > > But when I deploy it on cluster it gives me error. I tried different > > options to configure memory using –Xmx4096m in storm.bat itself but in > > vein. > > > > Can you please point out how this configuration works ? and how can I > > fix this problem? > > > > > > > > > > > > Regards, > > > > *Prakash Dayaramani* > > > > VoIP: +91-20-42521220 > > > > Chat <sip:[email protected]> Mail > > <mailto:[email protected]> > > > > cid:_4_0E30F19C0E30EE3C004CAAD265257D2A <http://www.infosys.com/bte> > > > > > > > > -- Javier González Nicolini
