You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2025/01/23 08:55:00 UTC

[jira] [Updated] (IGNITE-24295) Sql. TpcdsQueryPlannerTest query 64 timeouts

     [ https://issues.apache.org/jira/browse/IGNITE-24295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Orlov updated IGNITE-24295:
--------------------------------------
    Fix Version/s: 3.1

> Sql. TpcdsQueryPlannerTest query 64 timeouts
> --------------------------------------------
>
>                 Key: IGNITE-24295
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24295
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Konstantin Orlov
>            Assignee: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> It looks 20-30 seconds to prepare query 64 from TPC_DS suite on TC agent. And even though planning timeout is set to 60sec, we still get this test failed with {{java.util.concurrent.TimeoutException}}. The reason is the usage of {{IgniteTestUtils#await}} with default timeout, which is set to 30sec (see stacktraace below).
> {code}
> java.util.concurrent.TimeoutException
>   at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1886)
>   at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2021)
>   at org.apache.ignite.internal.testframework.IgniteTestUtils.await(IgniteTestUtils.java:836)
>   at org.apache.ignite.internal.testframework.IgniteTestUtils.await(IgniteTestUtils.java:865)
>   at org.apache.ignite.internal.sql.engine.framework.TestNode.prepare(TestNode.java:288)
> {code} 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)