You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Seliverstov (JIRA)" <ji...@apache.org> on 2019/02/01 13:21:00 UTC

[jira] [Commented] (IGNITE-10755) MVCC: Flaky continuous query tests

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

Igor Seliverstov commented on IGNITE-10755:
-------------------------------------------

[~rkondakov] The thing I not sure about is the CQ handler. Is it really necessary to keep pending events during the handler registration? I think it can be easily omitted by increasing registration write lock scope.

> MVCC: Flaky continuous query tests
> ----------------------------------
>
>                 Key: IGNITE-10755
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10755
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc
>            Reporter: Roman Kondakov
>            Assignee: Roman Kondakov
>            Priority: Major
>              Labels: CQ, MakeTeamcityGreenAgain, mvcc_stabilization_stage_1
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Some continuous query tests are flaky when MVCC is enabled:
> * {{CacheContinuousQueryConcurrentPartitionUpdateTest}} 
> ** {{testConcurrentUpdatesAndQueryStartMvccTxCacheGroup}}
> ** {{testConcurrentUpdatesAndQueryStartMvccTx}}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)