Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 29 Sep 2016 17:14:21 +0000 (UTC)
From: "Andrew Mashenkov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13007879.1474973128000.699301.1475169261838@Atlassian.JIRA>
In-Reply-To: <JIRA.13007879.1474973128000@Atlassian.JIRA>
References: <JIRA.13007879.1474973128000@Atlassian.JIRA> <JIRA.13007879.1474973128269@arcas>
Subject: [jira] [Commented] (IGNITE-3972) Continuous query events could be
 lost on backup node when primary leaves.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 29 Sep 2016 17:14:23 -0000


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

Andrew Mashenkov commented on IGNITE-3972:
------------------------------------------

I've commited fix affected atomic cache. But we still can loose events in transactional cache.
Events can be lost while entry was putting primary node for the entry key left topology.


> Continuous query events could be lost on backup node when primary leaves.
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-3972
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3972
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.7
>            Reporter: Vladimir Ozerov
>            Assignee: Andrew Mashenkov
>             Fix For: 1.8
>
>
> Consider the following scenario:
> 1) One node in topology;
> 2) PARTITIONED cache with 1 backup;
> 3) Continuous query is set on the cache;
> If another node joins the cluster, it will handle some updates. If it leaves the topology, the first node must flush it's own events from backup queue thus ensuring that no events are lost.
> But this doesn't happen because {{GridContinuousProcessor.addBackupNotification}} method perform lookup only on remote infos map, while handler is local and hence located in local infos map.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)