You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (Jira)" <ji...@apache.org> on 2020/04/13 11:17:00 UTC
[jira] [Commented] (IGNITE-12840) Leaking H2 internals when
querying from pyignite
[ https://issues.apache.org/jira/browse/IGNITE-12840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082241#comment-17082241 ]
Ilya Kasnacheev commented on IGNITE-12840:
------------------------------------------
I believe it is a duplicate of IGNITE-12848
> Leaking H2 internals when querying from pyignite
> ------------------------------------------------
>
> Key: IGNITE-12840
> URL: https://issues.apache.org/jira/browse/IGNITE-12840
> Project: Ignite
> Issue Type: Bug
> Components: clients, python
> Affects Versions: 2.8
> Reporter: Ilya Kasnacheev
> Priority: Critical
> Fix For: 2.8.1
>
> Attachments: TEST_TABLE.sql, read_cache_insert_update_table.py, test_insert_in_cache.py
>
>
> I am sharing a slightly modified reproducer from userlist.
> To run:
> Start a node (with JVM_OPTS=-Xmx512m to see it most clearly).
> Run a .sql file with sqlline (!run)
> python3 test_insert_in_cache.py
> in parallel terminal: python3 read_cache_insert_update_table.py
> Then you should observe slowing down and long GC pauses on server node. jmap will collect ever-increasing heap dumps.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)