RE: RE: Re: Ignite 2.8.0. Heap mem issue

[Andrey Davydov]

It seems detached connection NEVER become attached to thread other it was born. Because borrow method always return object related to caller thread. I.e. all detached connection borned in joined thread are not collectable forewer. So possible reproduce scenario: start separate thread. Run in this thread some logic that creates detached connection, finish and join thread. Remove link to thread. Repeat. Andrey. От: Andrey DavydovОтправлено: 23 марта 2020 г. в 21:37Кому: user@ignite.apache.orgТема: RE: Re: Ignite 2.8.0. Heap mem issue 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 <dren.butko...@gmail.com>:Hi Alex, i did another test and collected all the logs, GC logs, Heap mem dump, fiewscreenshots.All files are in zip file. File is to big for upload, please download fromJumbo mail link.https://jumboiskon.tportal.hr/download/eeab9848-2494-4ab7-a2cb-88766db0fafaThanks, Dren--Sent from: http://apache-ignite-users.70518.x6.nabble.com/  

RE: Re: Ignite 2.8.0. Heap mem issue

[dbutkovic]

Hi,

in attachment is code for heap mem issue simulation. Ignite_2.zip
  

# create cache TEST and insert random data into cache TEST
test_insert_in_cache.py

# read data from cache TEST and inset/update data in table TEST_TABLE via
SQL
read_cache_insert_update_table.py


Best regads

Dren




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

RE: Re: Ignite 2.8.0. Heap mem issue

[Andrey Davydov]

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 :Hi Alex, i did another test and collected all the logs, GC logs, Heap mem dump, fiewscreenshots.All files are in zip file. File is to big for upload, please download fromJumbo mail link.https://jumboiskon.tportal.hr/download/eeab9848-2494-4ab7-a2cb-88766db0fafaThanks, Dren--Sent from: http://apache-ignite-users.70518.x6.nabble.com/