[jira] [Updated] (IGNITE-426) Make sure continuous queries notifications are not missed in case primary node fails

["Valentin Kulichenko (JIRA)" <ji...@apache.org>]

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

Valentin Kulichenko updated IGNITE-426:
---------------------------------------
    Labels: important  (was: )

> Make sure continuous queries notifications are not missed in case primary node fails
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-426
>                 URL: https://issues.apache.org/jira/browse/IGNITE-426
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>            Reporter: Yakov Zhdanov
>            Assignee: Nikolay Tikhonov
>            Priority: Critical
>              Labels: important
>             Fix For: 1.5
>
>
> * Maintain updates queue on backup node(s) in addition to primary node.
> * If primary node crushes, this queue is flushed to listening clients.
> * To avoid notification duplicates we will have a per-partition update counter. Once an entry in some partition is updated, counter for this partition is incremented on both primary and backups. The value of this counter is also sent along with the update to the client, which also maintains the copy of this mapping. If at some moment it receives an update with the counter less than in its local map, this update is a duplicate and can be discarded.
> * To cleanup the backup queue we will use communication acks. When batch receival is acked by the client, we will send special ack message to backup nodes that will remove items that are not longer needed. This message has to contain partition to latest update counter map.



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