-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
14.0.13.Final
-
None
Hi,
I have a cache configured with lifespan=12m, max-idle=6m.
While having, cluster of 2 nodes in the same site, performing put 100k entries > waiting for 4m > touching 5k entries > waiting more 4 minutes -> 5k entries are in cache , the rest are expired as max-idle reached.
For x-site the same scenario:
performing put 100k entries > waiting for 4m > touching 5k entries > waiting more 4 minutes -> 5k entries should be in cache but there are 0 entries.
The cache configuration is:
<distributed-cache name="api-general-filestore" owners="2" segments="30" mode="SYNC" remote-timeout="25000" start="EAGER"> <encoding> <key media-type="text/plain; charset=UTF-8"/> <value media-type="text/plain; charset=UTF-8"/> </encoding> <backups> <backup site="site01" strategy="ASYNC" timeout="30000"> <take-offline after-failures="-1" min-wait="60000"/> </backup> </backups> <locking isolation="READ_COMMITTED" striping="false" acquire-timeout="20000" concurrency-level="1000"/> <transaction mode="NONE"/> <memory> <object size="4000000"/> </memory> <expiration max-idle="360000" lifespan="720000"/> <!-- <persistence passivation="false"> <file-store path="${infinispan.server.data.path}/api-general-filestore" shared="false" preload="false" purge="true"/> </persistence>--> </distributed-cache>
When the persistence is enabled with passivation, there is a warning in the logs: [org.infinispan.CONFIG] ISPN000652: Max idle is not supported when using a store
When the passivation is set to false, and exception is thrown during server startup:
org.infinispan.commons.CacheConfigurationException: ISPN000651: Max idle is not allowed while using a store without passivation
