You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/03 10:02:02 UTC

[jira] [Updated] (IGNITE-10252) Cache.get() may be mapped to the node with partition state is "MOVING"

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

Maxim Muzafarov updated IGNITE-10252:
-------------------------------------
    Fix Version/s:     (was: 2.8)
                   2.9

> Cache.get() may be mapped to the node with partition state is "MOVING"
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-10252
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10252
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Dmitriy Govorukhin
>            Priority: Major
>             Fix For: 2.9
>
>
> After implemented IGNITE-5357, in some cases get maybe mapped to the node with partition state is "MOVING" for PARTITION cache and it may lead to some assertion errors (we do not allow read from moving partitions). In an original issue, a talk was about only replicated cache, why it was implemented for partition cache, not clear.
> Details see in GridCacheContext#selectAffinityNodeBalanced(), method does not check that node is owner for partition.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)