As Ilya says, it’s not clear that there’s an issue here. Java will use up to the amount of memory you configure for its heap. There’s no suggestion that it’s running out of memory.
As you insert, update and remove data in a cluster you would expect the memory footprint to increase over time and then plateau when it reaches the heap and the data region size limit. > On 23 Apr 2021, at 03:20, yangpeng0...@sina.cn wrote: > > Hello! > <Catch.jpg> > > This is the memory usage within 6 hours of my choice. Do you think that > memory has been slowly increasing. Is this a configuration problem or an > Apache Ignite problem? Is there any way to verify whether it is an Ignite > docker image problem? > yangpeng0...@sina.cn <mailto:yangpeng0...@sina.cn> > > From: Ilya Kasnacheev <mailto:ilya.kasnach...@gmail.com> > Date: 2021-04-22 18:10 > To: user <mailto:user@ignite.apache.org> > Subject: Re: Re: Docker Running Apache Ignite Official Images memory > continues to increase > Hello! > > Apache Ignite node will collect metrics periodically, and send heartbeats > which will allocate objects on heap. If there is no load, Java GC is free to > not release this memory. It will reclaim it once there's load. > > Regards, > -- > Ilya Kasnacheev > > > чт, 22 апр. 2021 г. в 12:55, yangpeng0...@sina.cn > <mailto:yangpeng0...@sina.cn> <yangpeng0...@sina.cn > <mailto:yangpeng0...@sina.cn>>: > Hello! > The reason I tested this docker image is because I have a .Net Core console > program as the server side of Ignite. I also set the JvmInitialMemoryMb and > JvmMaxMemoryMb parameters to 1024mb and 2048mb. But after the program runs > docker, I did nothing. The memory is also the same as the official docker > image, the memory grows slowly and will not be released. > > yangpeng0...@sina.cn <mailto:yangpeng0...@sina.cn> > > From: Ilya Kasnacheev <mailto:ilya.kasnach...@gmail.com> > Date: 2021-04-22 17:23 > To: user <mailto:user@ignite.apache.org> > Subject: Re: Docker Running Apache Ignite Official Images memory continues to > increase > Hello! > > A JVM is free to use any amount of memory from 0 to -Xmx and this cannot be > qualified as memory leak without some solid evidence. > > Regards, > -- > Ilya Kasnacheev > > > чт, 22 апр. 2021 г. в 11:08, yangpeng0...@sina.cn > <mailto:yangpeng0...@sina.cn> <yangpeng0...@sina.cn > <mailto:yangpeng0...@sina.cn>>: > Hi: > I pull the docker image provided by Apache ignite, address: > https://hub.docker.com/r/apacheignite/ignite > <https://hub.docker.com/r/apacheignite/ignite>. Docker Pull Command:docker > pull apacheignite/ignite > <Catch(04-22-17-5(04-23-10-13-51).jpg> > Then execute the dock run command:docker run -itd --cpuset-cpus="0" -m 4096M > --memory-reservation 4096M --name apacheignite_ignite --net=host > apacheignite/ignite:2.10.0 > But after running for 2 days, we found that the memory used by it has been > increasing, as shown in the figure: > <Catch2805(04-22-(04-23-10-13-51).jpg> > Excuse me, how to solve the problem that the memory has been growing? > Is there a memory leak? > Or is this slow memory growth normal when docker is running? > yangpeng0...@sina.cn <mailto:yangpeng0...@sina.cn>
