[jira] [Comment Edited] (IGNITE-8073) Cache read metric is calculated incorrectly in atomic cache.

["Alexey Kuznetsov (JIRA)" <ji...@apache.org>]

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

Alexey Kuznetsov edited comment on IGNITE-8073 at 7/13/18 8:11 AM:
-------------------------------------------------------------------

[~dpavlov] Hi!
I think its rather important fix : cache read metric calculated incorrectly.
Could you plz review!


was (Author: alexey kuznetsov):
[~dpavlov] Hi!
I think its rather important fix : cache read metric calculated incorrectly.
Could you plz review/

> 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.7
>
>         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()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)