You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/11/16 07:28:58 UTC
[jira] [Updated] (IGNITE-4015) Continuous query events could be
lost on backup node when primary leaves (transactional cache).
[ https://issues.apache.org/jira/browse/IGNITE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-4015:
------------------------------------
Fix Version/s: (was: 1.8)
2.0
> Continuous query events could be lost on backup node when primary leaves (transactional cache).
> -----------------------------------------------------------------------------------------------
>
> Key: IGNITE-4015
> URL: https://issues.apache.org/jira/browse/IGNITE-4015
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.6, 1.7
> Reporter: Andrew Mashenkov
> Labels: transactions
> Fix For: 2.0
>
>
> Consider the following scenario:
> 1) One stable node in topology;
> 2) PARTITIONED, TRANSACTIONAL cache with 1 backup;
> 3) Continuous query is set on the cache;
> 4) Put some data to cache.
> If another node joins the cluster, it will handle some updates.
> But when it leaves the topology during put transaction, transaction rolled back with retry and events are lost.
> Reproducer can be found in org.apache.ignite.loadtests.continuous.CacheContinuousQueryFailoverTxPrimaryWriteOrderLoadTest
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)