-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Getting null for newly added elements in Cache. #7634
Comments
Hi @kuldeep9922, This is a known issue #4334 and scheduled to fix in 3.7. As a workaround you can increase |
Hi @ahmetmircik, Thanks for the reply. We already tried this workaround and it's not working. Is there any other way possible as of now? |
Hi, it will be fixed in 3.7. As an other alternative, if you can use jcache instead of imap, this problem should not be happen. |
This is definitely NOT fixed for the LRU strategy. Newly added items are still being evicted straight away before really old entries when Map is working at almost-full size (so it reached max-elements-count). |
Here's the map configuration:
After reaching max-size of 10000, it starts return null object for newly added values in cache. There seems to be some problem with eviction in hazel-cast. How can I fetch newly added values?
The text was updated successfully, but these errors were encountered: