[
https://issues.apache.org/jira/browse/IGNITE-10252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin updated IGNITE-10252:
----------------------------------------
Description:
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.
was: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.
> 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.8
>
>
> 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
(v7.6.3#76005)
