[
https://issues.apache.org/jira/browse/IGNITE-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830598#comment-15830598
]
Valentin Kulichenko commented on IGNITE-4036:
---------------------------------------------
[~amashenkov], I think that expiration info must be sent to the reader along
with the value, so that it's properly expired in the scenario you described. I
believe we already do this for backup entries, right?
> 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: Dmitry Karachentsev
> 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)
