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] [Updated] (IGNITE-4015) Continuous query events could be lost on backup node when primary leaves (transactional cache).
Date Mon, 03 Oct 2016 19:25:20 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Mashenkov updated IGNITE-4015:
-------------------------------------
    Summary: Continuous query events could be lost on backup node when primary leaves (transactional
cache).  (was: Continuous query events could be lost on backup node when primary leaves in
transactional cache.)

> 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
>
> onsider the following scenario:
> 1) One stable node in topology;
> 2) PARTITIONED, TRANSACONAL 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.



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

Mime
View raw message