[jira] [Commented] (IGNITE-4036) Near cache is not expired together with corresponding server cache
[ https://issues.apache.org/jira/browse/IGNITE-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894469#comment-15894469 ] ASF GitHub Bot commented on IGNITE-4036: Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1425 > 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.15#6346)
[jira] [Commented] (IGNITE-4036) Near cache is not expired together with corresponding server cache
[ 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)
[jira] [Commented] (IGNITE-4036) Near cache is not expired together with corresponding server cache
[ 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)
[jira] [Commented] (IGNITE-4036) Near cache is not expired together with corresponding server cache
[ https://issues.apache.org/jira/browse/IGNITE-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821846#comment-15821846 ] Andrew Mashenkov commented on IGNITE-4036: -- I've add test for this bug. It looks like it is related to IGNITE-518. > 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 > > 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)
[jira] [Commented] (IGNITE-4036) Near cache is not expired together with corresponding server cache
[ https://issues.apache.org/jira/browse/IGNITE-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821530#comment-15821530 ] ASF GitHub Bot commented on IGNITE-4036: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1425 IGNITE-4036: Near cache is not expired together with corresponding server cache Test added You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite igntie-4036 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1425.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1425 commit bedf7e74d81204ec66e0c143d3f57a2eff5389af Author: Andrey V. Mashenkov Date: 2017-01-11T14:01:26Z Test added commit 8641be3de7432957d02d125ec633431e02bfe6d2 Author: AMRepo Date: 2017-01-11T20:13:53Z Minors commit 00a9224dac3fade842ca6b4591c70f702a5a653f Author: Andrey V. Mashenkov Date: 2017-01-12T12:55:57Z Test fixed: CacheStore added to configuration commit 21ab4c9cebb9a58cd39623b07c226af4025b537e Author: Andrey V. Mashenkov Date: 2017-01-12T14:05:04Z Minors commit bb4e44db54b3d5b5c9b753de408e447a057657fc Author: AMRepo Date: 2017-01-12T17:00:07Z Minors commit 078f00685f234310b271ed37014ac79b5eba5f7c Author: AMRepo Date: 2017-01-12T17:20:46Z Minors commit abc543af4a19414ceaa4b1021770b77713dcb04b Author: AMRepo Date: 2017-01-12T17:23:21Z Fixed commit 81ecc634e8a6e8e9f9854bdb3301380ee09e8f6a Author: Andrey V. Mashenkov Date: 2017-01-13T09:43:47Z Minors commit fcecab80425accaeb18b2bb55e0b12d0be308d34 Author: Andrey V. Mashenkov Date: 2017-01-13T09:45:24Z Minors > 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 > > 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)
