[ https://issues.apache.org/jira/browse/IGNITE-20709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin updated IGNITE-20709: ----------------------------------------- Fix Version/s: 3.0.0-beta2 > Several tests in ItIgniteNodeRestartTest failed of flaky > -------------------------------------------------------- > > Key: IGNITE-20709 > URL: https://issues.apache.org/jira/browse/IGNITE-20709 > Project: Ignite > Issue Type: Bug > Reporter: Alexander Lapin > Assignee: Alexander Lapin > Priority: Critical > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > There might be multiple reasons for the ItIgniteNodeRestartTest failures but > the most obvious that definitely causes dozens of ones is replica operations > reordering. > {code:java} > org.awaitility.core.ConditionTimeoutException: Condition with lambda > expression in org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest > that uses org.apache.ignite.table.Table, org.apache.ignite.table.Tableint was > not fulfilled within 30 seconds. > at > app//org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167) > at > app//org.awaitility.core.CallableCondition.await(CallableCondition.java:78) > at > app//org.awaitility.core.CallableCondition.await(CallableCondition.java:26) > at > app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985) > at > app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:954) > at > app//org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest.checkTableWithData(ItIgniteNodeRestartTest.java:1182) > at > app//org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest.nodeWithDataTest(ItIgniteNodeRestartTest.java:751) > at > java.base@11.0.17/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > //... not so important stack trace lines {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)