thanks for replying . it's the first time i see this error but i searched
for the file in /storm/bin and didn't find anything also searched in other
files like logs and couldn't find the file . the error i copied it from the
UI because i didn't any errors in logs .
On Mon, Jul 24, 2017 at 3:24 AM,
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
eck jstack files of nimbus
and supervisor.
-邮件原件-
发件人: ght230 [mailto:ght...@163.com]
发送时间: 2015年12月18日 9:24
收件人: dev
抄送: user
主题: Re: Re: java.lang.OutOfMemoryError: Direct buffer memory
Hi
I have checked supervisor log and nimbus log, it seems nothing abnormal.
ght230
From: Manu
Hi
I have checked supervisor log and nimbus log, it seems nothing abnormal.
ght230
From: Manu Zhang
Date: 2015-12-18 08:27
To: dev
CC: user
Subject: Re: java.lang.OutOfMemoryError: Direct buffer memory
It could be other issues that trigger these netty connection problems and
finally OOM
It could be other issues that trigger these netty connection problems and
finally OOM. Could you check your supervisor log and nimbus log as well ?
On Thu, Dec 17, 2015 at 3:46 PM, ght230 wrote:
> Hi :
>
> I ran a simple wordcount topology on storm0.9.6, found 2 abnormal behaviors
> 1. Netty rec
