[
https://issues.apache.org/jira/browse/IGNITE-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143659#comment-15143659
]
Valentin Kulichenko commented on IGNITE-2468:
---------------------------------------------
Anton,
I looked at your changes. It seems to me that the test does not completely
verify the scenario when the query is executed from the client. After you
stopped this client (line 176), you should start one more server and make sure
that the remote filter is deployed there. Now this is not happening.
Otherwise looks good, assuming that all tests pass on TC.
> 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: Anton Vinogradov
> 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)
