You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/03/11 06:33:06 UTC
[jira] [Updated] (IGNITE-10753) MVCC: Sometimes vacuum does not
cleanup all outdated versions
[ https://issues.apache.org/jira/browse/IGNITE-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-10753:
-------------------------------------
Labels: MakeTeamcityGreenAgain transactions (was: MakeTeamcityGreenAgain mvcc_stabilization_stage_1 transactions)
> 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, transactions
> Fix For: 2.8
>
> Time Spent: 20m
> 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)