yes, if we set -Xmx == -Xms the heap size won't grow, but after our analysis, the problem is caused by direct memory occupation, we use netty in our system, i think maybe messages in ByteBuf are not released somewhere in our codes, which causes heavy memory leaks, but so far we haven't found the root cause.
do you guys know any good tools to minitor direct memory usage? uknow. ________________________________________ From: [email protected] <[email protected]> on behalf of Stack <[email protected]> Sent: Thursday, September 17, 2015 3:27 PM To: Hbase-User Subject: Re: JVM memory dump. Are you talking about the linux out-of-memory-killer? I don't know of a way to intercept the kill signal to have it dump java heap (there me be a way). Why is your heap growing? Have you not set -Xmx == -Xms? St.Ack On Wed, Sep 16, 2015 at 9:54 PM, James Teng <[email protected]> wrote: > HI All, > > > first i have to say sorry, because this topic is not closely related to > hbase but jvm. Does jvm support or we can take other approaches to let the > jvm dump its memory when the process is being killed by OS due to the > memory increment, which brings a threat to the system crash. > > > we have get an system which occupies lots of memory, and because of that, > sometime this process is killed by OS. we want to record the memory profile > for further analysis when the system signals to kill this system process. > > > any idea is appreciated! thanks in advance. > > > uknow. > >
