[
https://issues.apache.org/jira/browse/IGNITE-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739212#comment-16739212
]
Ignite TC Bot commented on IGNITE-10753:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2758681]]
*
JdbcThinTransactionsServerAutoCommitComplexSelfTest.testRepeatableReadAndFastDeleteWithConcurrentDelete
(last started)
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2752659&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
