In storm, OOM exception is typically caused by incorrectly accumulating references to the objects that should have been freed. This bug can be pinpointed and solved by analyzing the memory dump file. In particular, when OOM happens on a particular worker, a dump file will generated (in the same folder as storm binary, e.g., storm/bin/) which is an instantaneous memory snapshot. You can use dump analytics tools such as VisualVM to see if there are any classes with unexpected large number of instances. If yes, it is highly likely that you forgot to remove the references to the instances after usage.
Hope this helps. Li Wang Sent from my iPhone > On 24 Jul 2017, at 08:49, sam mohel <sammoh...@gmail.com> wrote: > > I got this error after submitted the topology > java.lang.OutOfMemoryError: Java heap space at > cern.colt.matrix.impl.DenseDoubleMatrix1D.<init>(Unknown Source) at > trident.state.BucketsDB.updateRandomVectors(BucketsDB.java:126) at > trident.state.q > > this error appeared after 8 hours from getting results > How can i solve it ?
