[ https://issues.apache.org/jira/browse/IGNITE-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739217#comment-16739217 ]
Roman Kondakov commented on IGNITE-10753: ----------------------------------------- [~gvvinblade], Please review the patch. Tests look good. JDBC timeout is not a blocker now - there are a lot of timeouts in the master branch at the moment. > MVCC: Sometimes vacuum does not cleanup all outdated versions > ------------------------------------------------------------- > > Key: IGNITE-10753 > URL: https://issues.apache.org/jira/browse/IGNITE-10753 > Project: Ignite > Issue Type: Bug > Components: mvcc > Reporter: Roman Kondakov > Assignee: Roman Kondakov > Priority: Major > Labels: MakeTeamcityGreenAgain, mvcc_stabilization_stage_1, > transactions > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > When mvcc test is finished, we check if there any outdated versions are left > in cache and not cleaned by vacuum. If so, an exception is thrown. There are > some tests with this problem: > * {{CacheMvccTransactionsTest.testCleanupWaitsForGet1}} > * {{CacheMvccTransactionsTest.testCleanupWaitsForGet3}} > * > {{CacheMvccReplicatedSqlCoordinatorFailoverTest.testAccountsTxSql_SingleNode_CoordinatorFails_Persistence}} > * > {{CacheMvccReplicatedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups0_RestartCoordinator_SqlDml}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)