Thank you for answer, Val.
Yeah, I expected OFFHEAP_TIERED mode work exactly same way as you said.
But, last couple of days's our test result is not seem to be so.
However, may be, that is not caused by OFFHEAP_TIERED mode.
First, Check the our test configuration.
We used [[ PARTITIONED & Near Cache & copyOnRead = false & OFFHEAP_TIERED
]].
<bean id="ignite.cfg"
class="org.apache.ignite.configuration.IgniteConfiguration">
<property name="cacheConfiguration">
<list>
<bean
class="org.apache.ignite.configuration.CacheConfiguration">
<property name="name" value="XXX"/>
<property name="backups" value="1"/>
<property name="nearConfiguration">
<bean
class="org.apache.ignite.configuration.NearCacheConfiguration" />
</property>
<property name="copyOnRead" value="false"/>
<property name="cacheMode" value="PARTITIONED"/>
<property name="atomicityMode" value="ATOMIC"/>
<property name="memoryMode" value="OFFHEAP_TIERED"/>
<property name="offHeapMaxMemory" value="0"/>
<property name="swapEnabled" value="false"/>
</bean>
</list>
</property>
...
</bean>
Under this configuration, Ignite's JVM heap is keep increasing,
and finally used most of heap is full with Cache Entry(Referenced by
org.apache.ignite.internal.processors.cache.distributed.near.GridNearAtomicCache).
But, we changed memory mode to OFFHEAP_VALUES,
then those memory usage pattern is disappear.
I attached Heap Dump Capture.(For your information, out JVM Heap max is set
to 1024M)
<http://apache-ignite-users.70518.x6.nabble.com/file/n6453/HeapDump_With_OFFHEAP_TIERED.png>
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Question-about-Tier-Propagation-of-Memory-tp6435p6453.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
