Added EntryExpiredListener in order to listen expired map entries. #6310
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ahmetmircik
force-pushed
the
feature/3.5.3/entryExpiredListener
branch
from
53e65de
to
3d2b219
Compare
ahmetmircik
force-pushed
the
feature/3.5.3/entryExpiredListener
branch
from
3d2b219
to
a427e28
Compare
|
This PR seems not applicable to maintenance. If we merge this PR, in a cluster which has both 3.5.3 and 3.5.2 nodes, 3.5.2 nodes will throw lots of NPEs due to the received EXPIRED events. The code part that throws NPE is here. Closing this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #6311
backport of #6308
EntryExpiredListenerwhich extendsMapListener.EntryEvictedListenernotification mechanism as is; means it will be receiving both expiration and eviction events as in now. If one implements bothEntryExpiredListenerandEntryEvictedListenerinterfaces, there is a probability that more than one event per entry at the same time may be seen. So you may receive both EVICTED and EXPIRED events for the same entry. This is because, eviction may also sweep expired entries. This may be appear when both size-based-eviction and expiration are configured for the sameIMap.