[
https://issues.apache.org/jira/browse/IGNITE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201041#comment-15201041
]
Semen Boikov commented on IGNITE-2791:
--------------------------------------
Nikolay,
Your fix doesn't look correct for me: each node calculates primary partitions
using locally ready affinity version, this does not guarantee consistentency.
All nodes should use the same topology version (topology version of discovery
event). I guess we can't not wait for affinity in discovery event listener, so
I think correct fix is collect per-node counter maps, and then on client node
wait for affinity and do filtering.
Also please add test case in GridCacheContinuousQueryConcurrentTest which will
execute the same scenario on changing topology (both server and client nodes
should join/leave).
Thanks
> Continuous query listener is not notified during concurrent key put.
> --------------------------------------------------------------------
>
> Key: IGNITE-2791
> URL: https://issues.apache.org/jira/browse/IGNITE-2791
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Nikolay Tikhonov
> Priority: Critical
> Fix For: 1.6
>
> Attachments: CacheListenersKillingMe3Main.java
>
>
> Attached the code reproducing the problem. What is evident from the log, is
> that that filter was invoked, but the listener was not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
