You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/05/23 09:15:00 UTC
[jira] [Commented] (IGNITE-5954) Ignite Cache Failover:
GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails
[ https://issues.apache.org/jira/browse/IGNITE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486953#comment-16486953 ]
Alexey Kuznetsov commented on IGNITE-5954:
------------------------------------------
the bug is in the following scenario:
1) near node requests key, save it in near cache
2) near node becames primary or backup
3) new value is inserted and propagated to the node. On this step, new value is set into DHT cache, not Near one. We have obsolete value in Near cache
4) near node again became near
5) we have obsolete value in Near cache. This is a bug
> Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-5954
> URL: https://issues.apache.org/jira/browse/IGNITE-5954
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Eduard Shangareev
> Assignee: Alexey Kuznetsov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Probably, it's broken after IGNITE-5272.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)