[
https://issues.apache.org/jira/browse/IGNITE-9828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666547#comment-16666547
]
ASF GitHub Bot commented on IGNITE-9828:
----------------------------------------
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/5189
IGNITE-9828: Continuous query failover.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9828
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5189.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 #5189
----
commit 8dfb5d3da4d92d7a7b3c41ff5c7dcd909a6042a1
Author: rkondakov <kondakov87@...>
Date: 2018-10-25T11:02:59Z
IGNITE-9828: Continuous query failover.
----
> MVCC: Continuous query failover.
> --------------------------------
>
> Key: IGNITE-9828
> URL: https://issues.apache.org/jira/browse/IGNITE-9828
> Project: Ignite
> Issue Type: Task
> Components: mvcc
> Reporter: Roman Kondakov
> Assignee: Roman Kondakov
> Priority: Major
> Fix For: 2.7
>
>
> We need to implement failover procedure for CQ with MVCC caches. Thoughts:
> * CQ failover tests should be adopted for mvcc scenarios. See
> {{IgniteCacheQuerySelfTestSuite4}}
> * We need to ensure the correctness of CQ and partition counters consistency
> in cases when some of TX participants are in prepared state and others are
> marked as rollback only. It looks like it doesn't work properly now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
