You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Pochatkin (Jira)" <ji...@apache.org> on 2026/03/16 16:50:00 UTC

[jira] [Updated] (IGNITE-28191) ItPartitionTableStatsMetricTest#recreateTableWithTheSameName is flaky

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

Mikhail Pochatkin updated IGNITE-28191:
---------------------------------------
    Fix Version/s: 3.2

> ItPartitionTableStatsMetricTest#recreateTableWithTheSameName is flaky
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-28191
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28191
>             Project: Ignite
>          Issue Type: Bug
>          Components: metrics ai3
>            Reporter: Vadim Pakhnushev
>            Assignee: Vadim Pakhnushev
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.2
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The test sometimes fails with the following exception:
> {noformat}
> java.lang.IllegalArgumentException: Metrics not found partition.statistics.table.28.partition.0
>   at org.apache.ignite.internal.table.ItPartitionTableStatsMetricTest.lambda$expectAggregatedMetricValue$4(ItPartitionTableStatsMetricTest.java:307)
> {noformat}
> This happens because after table recreation metrics are registered asynchronously. If metrics are registered on the remote node with a slight delay, enableStats call could miss the node that hosts the partition and we wouldn't find the metrics source.



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