[
https://issues.apache.org/jira/browse/IGNITE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723292#comment-14723292
]
ASF GitHub Bot commented on IGNITE-426:
---------------------------------------
GitHub user ntikhonov opened a pull request:
https://github.com/apache/ignite/pull/52
IGNITE-426 Implemented sending partition counter to backups node for …
…transaction caches. Added tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ntikhonov/ignite ignite-426
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/52.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #52
----
commit 987c3dca090c73d8b10af09648db32c3de9c3f55
Author: nikolay_tikhonov <ntikho...@gridgain.com>
Date: 2015-08-31T10:36:44Z
IGNITE-426 Implemented sending partition counter to backups node for
transaction caches. Added tests.
----
> 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: Semen Boikov
> Priority: Critical
> Fix For: ignite-1.4
>
>
> * 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)
