You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2017/01/13 09:50:26 UTC

[jira] [Commented] (IGNITE-518) TTL is not updated for reader when entry is accessed on backup

    [ https://issues.apache.org/jira/browse/IGNITE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821518#comment-15821518 ] 

Andrew Mashenkov commented on IGNITE-518:
-----------------------------------------

We must bother that NearCache expires on client nodes as well and add tests for it.
One of such test - IgniteCacheAtomicExpiryPolicyTest.testNearExpiresOnClient can be merged to IgniteCacheAtomicExpiryPolicyTest.testNearAccess when exripation issue will be fixed.


> TTL is not updated for reader when entry is accessed on backup
> --------------------------------------------------------------
>
>                 Key: IGNITE-518
>                 URL: https://issues.apache.org/jira/browse/IGNITE-518
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: sprint-2
>            Reporter: Alexey Goncharuk
>              Labels: Muted_test
>
> When ttl is updated, readers are recorded locally and update is then sent based on collected data. When get is performed on backup, readers are empty, so near readers are not updated.
> {{IgniteCacheAtomicExpiryPolicyTest.testNearAccess}} fails.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)