ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ksenia Rybakova (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6302) No IgniteOutOfMemoryException and client heap starts to grow constantly when server offheap memory gets full
Date Thu, 07 Sep 2017 15:15:01 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ksenia Rybakova updated IGNITE-6302:
------------------------------------
    Description: 
Load benchmark is streaming data to grid. Page memory maxSize is set. Sometimes IgniteOutOfMemoryException
is not thrown at servers when maxSize is reached. This is the first problem. The second one
- client's heap starts to grow constantly after server's offheap memory gets full.

Load config:
- org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark is used to stream
data
- 1 client, 4 server nodes
- client heap:  -Xms20g -Xmx20g, server heap: -Xms4g -Xmx4g
- memory policy maxSize: 5Gb
- page size: 2Kb
- number of entries to preload: 35M

At some point servers reach max offheap size (number of pages in log doesn't change and this
number matches 5Gb maxSize). IgniteOutOfMemoryException is not thrown and client starts to
utilize more and more heap capacity.

All configs and JFR dumps are attached.



  was:
Load benchmark is streaming data to grid. Page memory maxSize is set. Sometimes IgniteOutOfMemoryException
is not thrown at servers when maxSize is reached. This is the first problem. The second one
- client's heap starts to grow constantly after server's offheap memory gets full.

Load config:
- org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark is used to stream
data
- 1 client, 4 server nodes
- client heap:  -Xms20g -Xmx20g, server heap: -Xms4g -Xmx4g
- memory policy maxSize: 5Gb
- page size: 2Kb
- number of entries to preload: 35M

At some point servers reach max offheap size (number of pages in log doesn't change and this
number matches 5Gb maxSize). IgniteOutOfMemoryException is not thrown and client starts to
utilize more and more heap capacity.

All configs are attached.




> No IgniteOutOfMemoryException and client heap starts to grow constantly when server offheap
memory gets full 
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-6302
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6302
>             Project: Ignite
>          Issue Type: Bug
>          Components: general, streaming
>    Affects Versions: 2.1
>            Reporter: Ksenia Rybakova
>         Attachments: ignite-base-load-config.xml, jfr-driver0.jfr, jfr-server0.jfr, jfr-server1.jfr,
jfr-server2.jfr, jfr-server3.jfr, run-load.properties, run-load.xml
>
>
> Load benchmark is streaming data to grid. Page memory maxSize is set. Sometimes IgniteOutOfMemoryException
is not thrown at servers when maxSize is reached. This is the first problem. The second one
- client's heap starts to grow constantly after server's offheap memory gets full.
> Load config:
> - org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark is used
to stream data
> - 1 client, 4 server nodes
> - client heap:  -Xms20g -Xmx20g, server heap: -Xms4g -Xmx4g
> - memory policy maxSize: 5Gb
> - page size: 2Kb
> - number of entries to preload: 35M
> At some point servers reach max offheap size (number of pages in log doesn't change and
this number matches 5Gb maxSize). IgniteOutOfMemoryException is not thrown and client starts
to utilize more and more heap capacity.
> All configs and JFR dumps are attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message