You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2016/01/27 12:26:39 UTC
[jira] [Updated] (IGNITE-2468) Continuous query is no longer
deployed when node, that deployed it initially, leaves topology
[ https://issues.apache.org/jira/browse/IGNITE-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Magda updated IGNITE-2468:
--------------------------------
Labels: important (was: )
> Continuous query is no longer deployed when node, that deployed it initially, leaves topology
> ---------------------------------------------------------------------------------------------
>
> Key: IGNITE-2468
> URL: https://issues.apache.org/jira/browse/IGNITE-2468
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 1.5.0.final
> Reporter: Denis Magda
> Assignee: Nikolay Tikhonov
> Labels: important
> Fix For: 1.6
>
>
> Steps to reproduce:
> - Start a server node and run a continuous query setting autoUnsubscribe to false;
> - Start a client node that will update a single entry in a loop;
> - Start additional server node (without starting a query). Already existed query will be registered on this server node;
> - Check remote filter of both server nodes, they both have to receive updates (one server is primary while the other is backup);
> - Stop the first server that initiated the query;
> - Start one more server and you will see that the query won't be registered on it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)