ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-2468) Continuous query is no longer deployed when node, that deployed it initially, leaves topology
Date Tue, 02 Feb 2016 09:24:39 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Denis Magda updated IGNITE-2468:
--------------------------------
    Assignee: Anton Vinogradov  (was: Nikolay Tikhonov)

> 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)

Mime
View raw message