ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3972) Continuous query events could be lost on backup node when primary leaves.
Date Thu, 29 Sep 2016 17:14:21 GMT

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

Mime
View raw message