[
https://issues.apache.org/jira/browse/IGNITE-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507066#comment-16507066
]
ASF GitHub Bot commented on IGNITE-8073:
----------------------------------------
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/4174
IGNITE-8073 Cache read metric is calculated incorrectly in atomic cache.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite IGNITE-8073
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4174.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 #4174
----
commit e404757231de50e15416dae2f4795e17e1d777c4
Author: voipp <alkuznetsov.sb@...>
Date: 2018-06-09T14:36:11Z
#draft
----
> Cache read metric is calculated incorrectly in atomic cache.
> ------------------------------------------------------------
>
> Key: IGNITE-8073
> URL: https://issues.apache.org/jira/browse/IGNITE-8073
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.4
> Reporter: Alexey Kuznetsov
> Assignee: Alexey Kuznetsov
> Priority: Major
> Fix For: 2.6
>
> Attachments: GridCacheNearAtomicMetricsSelfTest.java
>
>
> In atomic cache with near enabled we perform put and remove operations.
> After it, get operation is called.
> Now, cache 'read' metric is calculated incorrectly, because it takes into
> account near cache entry.
> Reproducer is attached.
> Note that remove operation untracks 'reader' node from dht cache entry, but
> near cache entry still exists. The following test checks it :
> GridCacheAtomicNearCacheSelfTest#checkNearCache, see checkReaderRemove().
> See also
> http://apache-ignite-developers.2346864.n4.nabble.com/Near-cache-entry-removal-td28698.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
