[ https://issues.apache.org/jira/browse/IGNITE-24734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgeny Stanilovsky updated IGNITE-24734: ---------------------------------------- Description: Numerous “Send with retry timed out“ errors are detected while working with TpchBenchmark`s. As a result - first run for benchmarks is usually completes successfully while further runs can fail with statistics future timeout here: {code:java} statisticManager.lastUpdateStatisticFuture().get(10, TimeUnit.SECONDS); {code} if this section is commented (it`s not related to the issue, as honestly, benchmark at all) numerous errors “Send with retry timed out“ will be raised. Stack traces are attached. How to reproduce locally: Switch into TpchBenchmark and Override with your own: {code:java} @Override protected Path workDir() throws Exception { return Paths.get("/path/to/ignite-3/modules/runner/work"); } @Override TpcTable[] tablesToInit() { return new TpcTable[] {TpchTables.LINEITEM, TpchTables.PART, TpchTables.CUSTOMER, TpchTables.ORDERS}; } @Override Path pathToDataset() { return Paths.get("/path/to/benchbase/data/tpch-sf0.1"); } @Param({"6", "14", "22" /*"1", "2", "3", "4", "5", "6", "7", "8", "8v", "9", "10", "11", "12", "12v", "13", "14", "14v", "15", "16", "17", "18", "19", "20", "21", "22"*/ }) {code} Data (tpch-sf0.1) can be cloned from [here|https://github.com/ggprivate/benchbase/tree/benchbase-2025.2]. was: Numerous “Send with retry timed out“ errors are detected while working with TpchBenchmark`s. Stack traces are attached. How to reproduce locally: Switch into TpchBenchmark and Override with your own: {code:java} @Override protected Path workDir() throws Exception { return Paths.get("/path/to/ignite-3/modules/runner/work"); } @Override TpcTable[] tablesToInit() { return new TpcTable[] {TpchTables.LINEITEM, TpchTables.PART, TpchTables.CUSTOMER, TpchTables.ORDERS}; } @Override Path pathToDataset() { return Paths.get("/path/to/benchbase/data/tpch-sf0.1"); } @Param({"6", "14", "22" /*"1", "2", "3", "4", "5", "6", "7", "8", "8v", "9", "10", "11", "12", "12v", "13", "14", "14v", "15", "16", "17", "18", "19", "20", "21", "22"*/ }) {code} Data (tpch-sf0.1) can be cloned from [here|https://github.com/ggprivate/benchbase/tree/benchbase-2025.2]. > Numerous "Send with retry timed out" exceptions while repeatedly running > TpchBenchmark > -------------------------------------------------------------------------------------- > > Key: IGNITE-24734 > URL: https://issues.apache.org/jira/browse/IGNITE-24734 > Project: Ignite > Issue Type: Task > Components: general > Affects Versions: 3.0 > Reporter: Evgeny Stanilovsky > Priority: Major > Labels: ignite-3 > Attachments: stack1.txt, stack2.txt, stack3.txt, stack4.txt, > stack5.txt, stack6.txt, stack7.txt > > > Numerous “Send with retry timed out“ errors are detected while working with > TpchBenchmark`s. > As a result - first run for benchmarks is usually completes successfully > while further runs can fail with statistics future timeout here: > {code:java} > statisticManager.lastUpdateStatisticFuture().get(10, TimeUnit.SECONDS); > {code} > if this section is commented (it`s not related to the issue, as honestly, > benchmark at all) numerous errors “Send with retry timed out“ will be raised. > Stack traces are attached. > How to reproduce locally: > Switch into TpchBenchmark and Override with your own: > {code:java} > @Override > protected Path workDir() throws Exception { > return Paths.get("/path/to/ignite-3/modules/runner/work"); > } > @Override > TpcTable[] tablesToInit() { > return new TpcTable[] {TpchTables.LINEITEM, TpchTables.PART, > TpchTables.CUSTOMER, TpchTables.ORDERS}; > } > @Override > Path pathToDataset() { > return Paths.get("/path/to/benchbase/data/tpch-sf0.1"); > } > @Param({"6", "14", "22" > /*"1", "2", "3", "4", "5", "6", "7", "8", "8v", "9", "10", "11", > "12", "12v", > "13", "14", "14v", "15", "16", "17", "18", "19", "20", "21", > "22"*/ > }) > {code} > Data (tpch-sf0.1) can be cloned from > [here|https://github.com/ggprivate/benchbase/tree/benchbase-2025.2]. -- This message was sent by Atlassian Jira (v8.20.10#820010)