[
https://issues.apache.org/jira/browse/IGNITE-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409633#comment-15409633
]
ASF GitHub Bot commented on IGNITE-3406:
----------------------------------------
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/925
IGNITE-3406 - Interceptor and continuous query can get incorrect old …
…value during rebalancing
- Fix interceptor beforePup() on rebalancing.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3406
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/925.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 #925
----
commit 07d83af08fc328eff06485cd5404e8f7c70d706e
Author: dkarachentsev <[email protected]>
Date: 2016-08-05T12:36:38Z
IGNITE-3406 - Interceptor and continuous query can get incorrect old value
during rebalancing
- Fix interceptor beforePup() on rebalancing.
----
> Interceptor and continuous query can get incorrect old value during
> rebalancing
> -------------------------------------------------------------------------------
>
> Key: IGNITE-3406
> URL: https://issues.apache.org/jira/browse/IGNITE-3406
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.6
> Reporter: Valentin Kulichenko
> Assignee: Dmitry Karachentsev
> Fix For: 1.7
>
>
> During the rebalancing the old value passed to interceptor or continuous
> query can't be wrong due to scenarios described below.
> Scenario 1.
> # New node joins.
> # Update request arrives to the new node before the entry for the same key is
> rebalanced to this node.
> # Listeners are notified with {{null}} old value.
> In this case we should use {{GridDhtForceKeysRequest}} to get the old value.
> Scenario 2.
> # Entry is updated on primary node.
> # New backup node joins and the entry with already updated value is
> rebalanced from the primary node.
> # Update request arrives to this new backup node.
> # Listeners are notified with the old value which is the same as new value.
> In this case we should send the old value with the update request in case
> there is ongoing rebalancing and cache has interceptor configured or
> continuous queries registered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
