[
https://issues.apache.org/jira/browse/IGNITE-23373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032574#comment-18032574
]
Vladislav Pyatkov commented on IGNITE-23373:
--------------------------------------------
Merged e74127db340f1f3c31866690ddfbbb6971baff7e
> OutdatedTokenException when running
> ItDisasterRecoveryManagerTest#testRestartTablePartitionsWithCleanUp
> -------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-23373
> URL: https://issues.apache.org/jira/browse/IGNITE-23373
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Polovtsev
> Assignee: Vladislav Pyatkov
> Priority: Critical
> Labels: MakeTeamcityGreenAgain, ignite-3
> Fix For: 3.2
>
> Attachments:
> _Integration_Tests_Integration_Transactions_16103.log.zip, log.log
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h3. Motivation
> This exception leads to the system's critical error and has a high impact on
> the application.
> Similar exceptions can be reproduced in various tests due to misusing the
> version value conception (it assumes that the revision would be in the
> predicted horizon). Currently, we can call it asynchronously in unpredictable
> future, so any history capacity might be exhausted.
> Look at the using pattern of `localPartitionsVv` here:
> TableManager#restartPartitionWithCleanUp
> h3. Implementation notes
> The `localPartitionsVv` is used to linearize, create a table, and create all
> partitions in the table (table first, partitions after).
> I think we can start to exclude this concept and get rid of the
> `localPartitionsVv`.
> h3. Definition of done
> We should get rid of using `localPartitionsVv` in the restart partition flow
> (at least because the VV is linearizing the table start process, but it does
> not apply for a partition restart).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
