ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Plekhanov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8073) Cache read metric is calculated incorrectly in atomic cache.
Date Wed, 27 Jun 2018 10:31:00 GMT

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

Aleksey Plekhanov commented on IGNITE-8073:
-------------------------------------------

[~Alexey Kuznetsov], looks good to me.

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

Mime
View raw message