[
https://issues.apache.org/jira/browse/IGNITE-27646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-27646:
-----------------------------------------
Description:
Test fails with the following error:
{noformat}
java.lang.AssertionError:
Expected: is <true>
but: was <false>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
at
org.apache.ignite.internal.rebalance.ItRebalanceMetricsTest.testRebalanceMetrics(ItRebalanceMetricsTest.java:156)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511){noformat}
The root cause is that blocking a watch notification thread does not guarantee
that metastorage cannot be updated.
So, the easiest way to "freeze" updating pending/stable keys is by blocking the
rebalance thread pool (which is single threaded executor).
was:
Test fails with the following error:
{noformat}
java.lang.AssertionError:
Expected: is <true>
but: was <false>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
at
org.apache.ignite.internal.rebalance.ItRebalanceMetricsTest.testRebalanceMetrics(ItRebalanceMetricsTest.java:156)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511){noformat}
The root cause is that blocking a watch notification thread does not guarantee
that metastorage cannot be updated.
So, the easiest way to achieve
> ItRebalanceMetricsTest.testRebalanceMetrics is flaky
> ----------------------------------------------------
>
> Key: IGNITE-27646
> URL: https://issues.apache.org/jira/browse/IGNITE-27646
> Project: Ignite
> Issue Type: Bug
> Components: metrics ai3
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Labels: MakeTeamcityGreenAgain, ignite-3
> Fix For: 3.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test fails with the following error:
> {noformat}
> java.lang.AssertionError:
> Expected: is <true>
> but: was <false>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
> at
> org.apache.ignite.internal.rebalance.ItRebalanceMetricsTest.testRebalanceMetrics(ItRebalanceMetricsTest.java:156)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511){noformat}
> The root cause is that blocking a watch notification thread does not
> guarantee that metastorage cannot be updated.
> So, the easiest way to "freeze" updating pending/stable keys is by blocking
> the rebalance thread pool (which is single threaded executor).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
