ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Kulichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-426) Make sure continuous queries notifications are not missed in case primary node fails
Date Thu, 23 Jul 2015 05:56:04 GMT

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

Valentin Kulichenko updated IGNITE-426:
---------------------------------------
    Description: 
* 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.
* Also need to figure out the best way to clean the backup queue if topology is stable. TBD.

> 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: Task
>            Reporter: Yakov Zhdanov
>            Assignee: Valentin Kulichenko
>            Priority: Critical
>
> * 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.
> * Also need to figure out the best way to clean the backup queue if topology is stable.
TBD.



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

Mime
View raw message