[
https://issues.apache.org/jira/browse/IGNITE-21764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-21764:
-----------------------------------------
Fix Version/s: 3.0.0-beta2
> PersistentPageMemoryMvTableStorageTest.testIndexDestructionOnRecovery is flaky
> ------------------------------------------------------------------------------
>
> Key: IGNITE-21764
> URL: https://issues.apache.org/jira/browse/IGNITE-21764
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Polovtcev
> Assignee: Aleksandr Polovtcev
> Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> A failure can be found here:
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7936530
> There's a race between destroying and creating an index, I believe this is a
> test problem, because we shouldn't have identical index IDs in such
> situations in real life.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
