[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=16760585#comment-16760585 ] Ignite TC Bot commented on IGNITE-10755: {panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2998320&buildTypeId=IgniteTests24Java8_RunAll] > 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)
[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=16760586#comment-16760586 ] Roman Kondakov commented on IGNITE-10755: - [~gvvinblade], tests look goo. Patch is ready for review. > 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)
[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=16760049#comment-16760049 ] Roman Kondakov commented on IGNITE-10755: - [~gvvinblade], # Listeners initialization (obtaining the current update counters map) was moved under the listeners write lock. This allows to avoid collecting pending events in the dedicated map. # Listener registration lock has been moved from the cache context to the group context to avoid races between adding cache to the {{CacheGroupContext#contQryCaches}} and listeners registration. When each cache has it's own listener lock, adding and notifying listeners are not synchronized between different caches within same group. And there were possible situations when uninitialized listener was supplied with a skip update event fired in the neighbor cache. > 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)
[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)
[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=16754147#comment-16754147 ] Roman Kondakov commented on IGNITE-10755: - [~gvvinblade], I made fixes proposed by yours. Patch is ready for review. Tests look good. > 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)
[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=16754145#comment-16754145 ] Ignite TC Bot commented on IGNITE-10755: {panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2929946&buildTypeId=IgniteTests24Java8_RunAll] > 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)
[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=16748669#comment-16748669 ] Ignite TC Bot commented on IGNITE-10755: {panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2861304&buildTypeId=IgniteTests24Java8_RunAll] > 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)
[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=16748432#comment-16748432 ] Ignite TC Bot commented on IGNITE-10755: {panel:title=-> Run :: MVCC Cache: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *-> Run :: MVCC Cache* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2861319&buildTypeId=IgniteTests24Java8_RunMvccCache] > 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)
[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=16747983#comment-16747983 ] Igor Seliverstov commented on IGNITE-10755: --- [~rkondakov], please merge last master and rerun tests. > 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)
[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=16745056#comment-16745056 ] Roman Kondakov commented on IGNITE-10755: - [~gvvinblade], patch is ready for review. Tests look good. Multiple fails in MVCC Cache suite are caused by some problems in the master branch. > 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)
[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=16745049#comment-16745049 ] Ignite TC Bot commented on IGNITE-10755: {panel:title=-> Run :: MVCC Cache: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}MVCC PDS 1{color} [[tests 32|https://ci.ignite.apache.org/viewLog.html?buildId=2822879]] * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateSimple_5_Servers_5_Clients_FromClient - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testClientReconnectClusterActivateInProgress - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateSimple_5_Servers_5_Clients - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateSimple_5_Servers - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateFailover1 - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateFailover2 - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testClientReconnectClusterActive - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateSimple_5_Servers2 - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover1 - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testActivateSimple_5_Servers_5_Clients - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testJoinWhileDeactivate1_Server - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testJoinWhileActivate1_Client - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testJoinWhileDeactivate1_Client - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testInactiveTopologyChanges - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testActivateSimple_SingleNode - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testConcurrentJoinAndActivate - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testActivateSimple_5_Servers_5_Clients_FromClient - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testActivateSimple_5_Servers - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testActivateSimple_5_Servers2 - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testClientReconnectClusterDeactivateInProgress - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateSimple_SingleNode - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testClientReconnectClusterDeactivated - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testClientReconnectClusterActivated - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testActivateCachesRestore_SingleNode - 2,3% fails in last 608 master runs. * IgnitePdsMvccTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testActivateCachesRestore_5_Servers - 2,3% fails in last 608 master runs. {color:#d04437}MVCC PDS 4{color} [[tests 30|https://ci.ignite.apache.org/viewLog.html?buildId=2822882]] * IgnitePdsMvccTestSuite4: IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testInactiveTopologyChanges - 2,3% fails in last 607 master runs. * IgnitePdsMvccTestSuite4: IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testJoinWhileDeactivate1_Client - 2,3% fails in last 607 master runs. * IgnitePdsMvccTestSuite4: IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testActivateFailover2 - 2,3% fails in last 607 master runs. * IgnitePdsMvccTestSuite4: IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testDeactivateFailover2 - 2,3% fails in last 607 master ru
[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=16745042#comment-16745042 ] Ignite TC Bot commented on IGNITE-10755: {panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2822868&buildTypeId=IgniteTests24Java8_RunAll] > 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)