Hello Val,
This is my cache configuration. The near cache of the client is implemented
by java source code with setNearEvictionPolicy(5000)
<property name="cacheConfiguration">
<bean class="org.apache.ignite.configuration.CacheConfiguration">
<property name="name" value="cache_name"/>
<property name="statisticsEnabled" value="true" />
<property name="atomicityMode" value="ATOMIC"/>
<property name="writeSynchronizationMode" value="FULL_ASYNC"/>
<property name="offHeapMaxMemory" value="#{ 14 * 1024L * 1024L *
1024L }"/>
<property name="expiryPolicyFactory">
<bean class="javax.cache.expiry.ModifiedExpiryPolicy"
factory-method="factoryOf">
<constructor-arg>
<bean class="javax.cache.expiry.Duration">
<constructor-arg value="SECONDS"/>
<constructor-arg value="3600"/>
</bean>
</constructor-arg>
</bean>
</property>
<property name="evictionPolicy">
<bean
class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
<property name="maxSize" value="#{ 10 * 1024L }"/>
</bean>
</property>
</bean>
</property>
I have found that some entries can exist on the near cache but not exist on
the server node.
In this case, the issue is reproduced. This may be a bug related to
expiration using near cache.
It would be nice to solve this expiration issue or implement the way to
clear near cache using Rest API.
Thanks,
Satoshi
2016-10-05 7:50 GMT+09:00 vkulichenko <[email protected]>:
> Hi Satoshi,
>
> I still can't reproduce this. Can you show your cache configuration and
> describe how you populate the data?
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Question-about-rmvall-command-of-Rest-
> API-tp7903p8094.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
