Max-Idle for expiration - does not respect GET cache

[malaia]

My cache config

  <expiration lifespan="120000" max-idle="60000" interval="30000" />

max-idle is configured as 1 min.

My requests

Test 1:

PUT 31/Jan/2017:16:18:38 - created

GET 31/Jan/2017:16:18:45 - found (within 1 min)

GET 31/Jan/2017:16:19:41 - cache expired (after 1 min from PUT, but within 1 min from previous GET)

Test 2:

PUT 31/Jan/2017:16:22:33 - created

PUT 31/Jan/2017:16:23:03 - created

GET 31/Jan/2017:16:23:40 - found (after 1 min from first PUT, within 1 min from 2nd PUT)

GET 31/Jan/2017:16:24:05 - cache expired (after 1 min from 2nd PUT, but within 1 min from previous GET)

Question:

Is GET cache (Cache.getAdvancedCache().getCacheEntry(key)) considered as operation before executing max-idle logic?

If any specific config has to be done to achieve this, please let me know the same.

Thanks

[william.burns]

Are you using a clustered cache by chance, for example replicated?  Unfortunately max-idle only works reliably in a single node.  This is due to a get sometimes is only performed locally. So this means that other nodes may not be refreshed and the key may expire on a subset of nodes.  Therefore, for consistency it is not recommended to use max-idle in a clustered cache [1].

[1] Infinispan 9.0 User Guide

[malaia]

Thanks for your reply.

In production, yes I am using clustered cache but the test I performed was on a single node.

I am using Version 8.1.x & as per your documentation "this entry will expire 1000 millis after it is last accessed" when there is a configuration for Max-idle.

Does the word "accessed" also include "GET" operation when only single node is in use?