ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-8073) Cache read metric is calculated incorrectly in atomic cache.
Date Fri, 08 Jun 2018 12:14:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexey Kuznetsov reassigned IGNITE-8073:
----------------------------------------

    Assignee: Alexey Kuznetsov

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

Mime
View raw message