ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3972) Continuous query events could be lost on backup node when primary leaves.
Date Thu, 29 Sep 2016 14:00:31 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532850#comment-15532850
] 

ASF GitHub Bot commented on IGNITE-3972:
----------------------------------------

GitHub user AMashenkov opened a pull request:

    https://github.com/apache/ignite/pull/1133

    IGNITE-3972: Continuous query events could be lost on backup node when primary leaves.

    Reproduced.
    Fix provided prevents CQ events from being lost, but single duplicate event can occur
if node has left on entry put.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-3972

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1133.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1133
    
----
commit 8027a75aafc4ec6118aa796fcc4d5bd403993385
Author: Andrey V. Mashenkov <andrey.mashenkov@gmail.com>
Date:   2016-09-27T14:47:53Z

    Implemented

commit 39590383e487a2ad7e7970118718a19325918c24
Author: Andrey V. Mashenkov <andrey.mashenkov@gmail.com>
Date:   2016-09-27T14:50:26Z

    Test reproducing bug added: see CQLostRunner

----


> Continuous query events could be lost on backup node when primary leaves.
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-3972
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3972
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.7
>            Reporter: Vladimir Ozerov
>            Assignee: Andrew Mashenkov
>             Fix For: 1.8
>
>
> Consider the following scenario:
> 1) One node in topology;
> 2) PARTITIONED cache with 1 backup;
> 3) Continuous query is set on the cache;
> If another node joins the cluster, it will handle some updates. If it leaves the topology,
the first node must flush it's own events from backup queue thus ensuring that no events are
lost.
> But this doesn't happen because {{GridContinuousProcessor.addBackupNotification}} method
perform lookup only on remote infos map, while handler is local and hence located in local
infos map.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message