[ https://issues.apache.org/jira/browse/IGNITE-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruslan Gilemzyanov updated IGNITE-8035: --------------------------------------- Summary: Duplicated events with type CREATED in ContinuousQuery's Events Listener (was: Duplicated events in ContinuousQuery's Events Listener ) > Duplicated events with type CREATED in ContinuousQuery's Events Listener > ------------------------------------------------------------------------- > > Key: IGNITE-8035 > URL: https://issues.apache.org/jira/browse/IGNITE-8035 > Project: Ignite > Issue Type: Bug > Components: cache > Affects Versions: 2.4 > Reporter: Ruslan Gilemzyanov > Priority: Major > > We faced with bug in ContinuousQuery's EventListener work in Ignite. I wrote > sample project to demonstrate it. > We started 2 server nodes connected to the one cache. > Topology snapshot became [ver=2, servers=2, clients=0, CPUs=4, heap=3.6GB] > I have put elements in cache (about 50 elements). Elements were distributed > between two nodes approxiamtely in the same amount. > After pushing every element to cache we waited 100ms (to ensure that Listener > did his work) and deleted element from cache. > Then we stopped one node. (Topology snapshot became [ver=3, servers=1, > clients=0, CPUs=4, heap=1.8GB]) > And then some absolutely randomly chosen (deleted from cache to this moment) > events came to other working node with status CREATED (Remind you that we > deleted them from cache to this moment). In our case it was 5 events. > I think this is direct violation of Continuous Query's "exactly once > delivery" contract. > Source code is here: [https://github.com/ruslangm/ignite-sample] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)