[
https://issues.apache.org/jira/browse/IGNITE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930124#comment-15930124
]
ASF GitHub Bot commented on IGNITE-518:
---------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1636
IGNITE-518: unmute fixed tests.
Unmute tests that was fixed in IGNITE-4036
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-518
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1636.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 #1636
----
commit e247ba7e8492446d033f6b30314f37c567e9b650
Author: Andrey V. Mashenkov <[email protected]>
Date: 2017-03-17T15:13:50Z
Minor fix.
Unmute tests that was fixed in IGNITE-4036
----
> 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
> Assignee: Andrew Mashenkov
> Labels: Muted_test
> Fix For: 2.0
>
>
> 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.15#6346)
