As I see in heapDump:

 

There are 29000+ connections stored here:

 

this     - value: org.apache.ignite.internal.processors.query.h2.H2ConnectionWrapper #1

<- key     - class: java.util.concurrent.ConcurrentHashMap$Node, value: org.apache.ignite.internal.processors.query.h2.H2ConnectionWrapper #1

  <- [41919]     - class: java.util.concurrent.ConcurrentHashMap$Node[], value: java.util.concurrent.ConcurrentHashMap$Node #32575

   <- table     - class: java.util.concurrent.ConcurrentHashMap, value: java.util.concurrent.ConcurrentHashMap$Node[] #11010

    <- detachedConns     - class: org.apache.ignite.internal.processors.query.h2.ConnectionManager, value: java.util.concurrent.ConcurrentHashMap #2109

 

But there are only 28 TCP connections in system.

 

I have already report some way for memory leaks in ConnectionManager in other mail thread, this is one more way. It seem that more problems is in ConnectionManager class.

 

 

Andrey.

 

От: Evgenii Zhuravlev
Отправлено: 23 марта 2020 г. в 20:37
Кому: user
Тема: Re: Ignite 2.8.0. Heap mem issue

 

Hi,

 

I tried to reproduce the same problem using the provided information, but without success. In the log I see that there are operations running on the cluster that were not described in pseudo code, for example, SQL queries withh count. Are you running something else? Can you provide full reproducer or try to run all operations by one to find the operation, which can cause this behaviour?

 

Evgenii

 

ср, 18 мар. 2020 г. в 07:07, dbutkovic <[email protected]>:

Hi Alex,

i did another test and collected all the logs, GC logs, Heap mem dump, fiew
screenshots.

All files are in zip file. File is to big for upload, please download from
Jumbo mail link.

https://jumboiskon.tportal.hr/download/eeab9848-2494-4ab7-a2cb-88766db0fafa

Thanks, Dren



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

 

Reply via email to