JDK)
2) Verbose GC logs
3) Heap dumps
Also it is better to try this on a single worker first.
-Original Message-
From: Matthias J. Sax [mailto:mj...@informatik.hu-berlin.de]
Sent: Friday, June 05, 2015 11:24 AM
To: user@storm.apache.org
Subject: Re: Storm out of memory error
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 wi
better enable gc logging and jmx port, and watch how gc behaves.
Fang
On Fri, Jun 5, 2015 at 8:11 AM, Prakash Ramesh Dayaramani <
prakash_dayaram...@infosys.com> wrote:
> Hi All,
>
> I am trying to deploy jar on storm cluster which loads
> volume of data at startup and stores it
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
