Backup lost if "maxIdle" property is used #9153
I'm facing an issue with an IMap distributed on two different nodes.
I'm using this IMap with :
In the beginning I'm putting some values in the map but after that the values are only accessed and not updated for quite a long period (like 10 or 15 minutes).
What is the problem ?
In the beginning (before 10 seconds elapsed), the backup is working great ...
But after 10 seconds : all the backups are lost !
If I change the amount of seconds for the MaxIdle property to an higher value (let's say 300 seconds) then everything is working well until 300 seconds.
The backups gets evicted if I use MaxIdle property, is that a normal behavior ?
For information : using a "sync" backup didn't solve the problem at all.
I don't have any workaround here and it's quite a severe issue to integrate Hazelcast in our system.
Hazelcast version : 3.7.2
I'm just not sure about the performance of this way of doing... Is that efficient ? (I'm doing almost 3k get/s)
I tried via the EntryProcessor. It worked well, the backup is now touched and I haven't seen any lack of performance.
I still see two negative points about this :
You may update your documentation to tell about this behavior as this is not expected at all (and quite dangerous : backup is lost), don't you think ?
Are you still going to change the get() method to touch the backup ?