[
https://issues.apache.org/jira/browse/IGNITE-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826075#comment-15826075
]
Andrew Mashenkov commented on IGNITE-4036:
------------------------------------------
If entry that was put from client node expires correctly in the node NearCache.
But if entry was put on some another node, then it is possible it will not be
expires in client NearCache.
It look like client has missed to subscribe on cache events while getting entry
value from grid or smth like that.
Could someone clarify how it should work?
> Near cache is not expired together with corresponding server cache
> ------------------------------------------------------------------
>
> Key: IGNITE-4036
> URL: https://issues.apache.org/jira/browse/IGNITE-4036
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.7
> Reporter: Sergej Sidorov
> Assignee: Andrew Mashenkov
> Fix For: 1.9
>
>
> Steps to reproduce:
> 1. Configure server cache with expiry time
> 2. Start server node
> 3. Configure client node with near cache
> 4. Start client node
> 5. Put elements to cache
> 6. Wait for the expiry of the cache
> 7. Check cache state (server/client)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
