I am using ignite with a native persistence and loading ~60k rows into a new
cache via the jdbc driver. When I attempt to run a query against the cache,
I can see my heap memory usage grow (using the JMX console) until it is
exhausted and the H2 database crashes. I am using DBeaver to connect and
query the cache via the SQL interface.
I do not have any data regions configured other than the default and here is
the configuration I have for that:
<property name="defaultDataRegionConfiguration">
<bean
class="org.apache.ignite.configuration.DataRegionConfiguration">
<property name="persistenceEnabled"
value="true"/>
<property name="name" value="Default_Region"/>
<property name="initialSize" value="#{10L * 1024
* 1024 * 1024}"/>
<property name="maxSize" value="#{10L * 1024 *
1024 * 1024}"/>
<property name="checkpointPageBufferSize"
value="#{1L * 1024 * 1024 * 1024}"/>
<property name="pageEvictionMode"
value="RANDOM_2_LRU"/>
</bean>
</property>
I do not have on-heap caching specifically enabled anywhere in my config.
The server running ignite has 64GB of memory total and 1TB of space for
persisted data.
My understanding was that I should be using off-heap memory since I have
persistence enabled but that doesn't appear to be the behavior when
querying. The cache utilizes about 25GB on disk when persisted so if it is
trying to pull all of that into my 10GB heap then it will obviously fail.
Is someone able to help me understand what might be occurring to cause the
heap memory exhaustion that I see?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
