Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReadBackupData and MaxIdleSeconds relation - documentation #8354

Closed
BogdanEM opened this issue Jun 9, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@BogdanEM
Copy link

commented Jun 9, 2016

MapConfig com.hazelcast.config.MapConfig.setMaxIdleSeconds(int maxIdleSeconds)

Maximum number of seconds for each entry to stay idle in the map. Entries that are idle(not touched) for more than maxIdleSeconds will get automatically evicted from the map. Entry is touched if get, getAll, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. Default is 0.

Seems that when we have a backup with ReadBackupData to true, doing a map.get() does not "touch" the map entry. So even though we have constant reads from that entry, when maxIdleSeconds is reached the entry is evicted from the map.

This seems to be the desired behavior, as I see the code inside MapProxyImpl, but I wasn't able to find this "gotcha" in the documentation. Could you please point this out in the documentation? If it's already documented and was my failure to find it, just ignore me :)

I'm using Hazelcast 3.6.2.

@enesakar

This comment has been minimized.

Copy link
Member

commented Jun 21, 2016

You are right, we should document it.

@enesakar enesakar added this to the 3.7 milestone Jun 21, 2016

@Serdaro

This comment has been minimized.

Copy link
Member

commented Jul 22, 2016

@BogdanEM , the last paragraph of the section http://docs.hazelcast.org/docs/3.6/manual/html-single/index.html#enabling-backup-reads actually provides the gotcha (starting with "Please note that"). But let me make it more visible. Thank you.

@Serdaro Serdaro closed this Jul 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.