[GitHub] ignite pull request #1133: IGNITE-3972: Continuous query events could be los...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #1133: IGNITE-3972: Continuous query events could be los...

andrey-kuznetsov
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 <[hidden email]>
Date:   2016-09-27T14:47:53Z

    Implemented

commit 39590383e487a2ad7e7970118718a19325918c24
Author: Andrey V. Mashenkov <[hidden email]>
Date:   2016-09-27T14:50:26Z

    Test reproducing bug added: see CQLostRunner

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #1133: IGNITE-3972: Continuous query events could be los...

andrey-kuznetsov
Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---