[
https://issues.apache.org/jira/browse/IGNITE-26941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-26941:
-------------------------------------
Description:
{code:java}
org.opentest4j.AssertionFailedError: expected: <true> but was: <false> at
app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63) at
app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36) at
app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31) at
app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:183) at
app//org.apache.ignite.raft.jraft.core.TestCluster.ensureSame(TestCluster.java:558)
at
app//org.apache.ignite.raft.jraft.core.TestCluster.ensureSame(TestCluster.java:530)
at
app//org.apache.ignite.raft.jraft.core.ItNodeTest.testLeaderFail(ItNodeTest.java:1762)
{code}
This is probably caused by instability of the physical topology. In the logs
(in attachments) we can see extra Node joined events along with suspicious
Topology snapshot records that on its own causes following
{code:java}
default:int_tlf_5003:[email protected]:5003][2d796c8e-d25f-40fa-8243-db2708cdab75]
Timeout getting GetMetadataResp from 127.0.1.1:5005 within 1000 ms, cause:
java.util.concurrent.TimeoutException: Did not observe any item or terminal
signal within 1000ms in 'source(MonoDefer)' (and no fallback has been
configured)
[01:34:25]W: [:ignite-raft:integrationTest]
[2025-11-03T23:34:25,369][WARN ][sc-cluster-5003-447][MembershipProtocol]
[default:int_tlf_5003:[email protected]:5003][updateMembership][SYNC]
Skipping to add/update member: {m:
default:int_tlf_5005:[email protected]:5005, s: ALIVE, inc: 0}, due to
failed fetchMetadata call (cause: java.util.concurrent.TimeoutException: Did
not observe any item or terminal signal within 1000ms in 'source(MonoDefer)'
(and no fallback has been configured)) {code}
was:
{code:java}
org.opentest4j.AssertionFailedError: expected: <true> but was: <false> at
app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63) at
app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36) at
app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31) at
app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:183) at
app//org.apache.ignite.raft.jraft.core.TestCluster.ensureSame(TestCluster.java:558)
at
app//org.apache.ignite.raft.jraft.core.TestCluster.ensureSame(TestCluster.java:530)
at
app//org.apache.ignite.raft.jraft.core.ItNodeTest.testLeaderFail(ItNodeTest.java:1762)
{code}
This is probably caused by instability of the physical topology. In the logs
(in attachments) we can see extra Node joined events along with suspicious
Topology snapshot records that on its own causes following
{code:java}
default:int_tlf_5003:[email protected]:5003][2d796c8e-d25f-40fa-8243-db2708cdab75]
Timeout getting GetMetadataResp from 127.0.1.1:5005 within 1000 ms, cause:
java.util.concurrent.TimeoutException: Did not observe any item or terminal
signal within 1000ms in 'source(MonoDefer)' (and no fallback has been
configured)
[01:34:25]W: [:ignite-raft:integrationTest]
[2025-11-03T23:34:25,369][WARN ][sc-cluster-5003-447][MembershipProtocol]
[default:int_tlf_5003:[email protected]:5003][updateMembership][SYNC]
Skipping to add/update member: {m:
default:int_tlf_5005:[email protected]:5005, s: ALIVE, inc: 0}, due to
failed fetchMetadata call (cause: java.util.concurrent.TimeoutException: Did
not observe any item or terminal signal within 1000ms in 'source(MonoDefer)'
(and no fallback has been configured)) {code}
> ItNodeTest.testLeaderFail failed
> --------------------------------
>
> Key: IGNITE-26941
> URL: https://issues.apache.org/jira/browse/IGNITE-26941
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexander Lapin
> Priority: Major
> Labels: MakeTeamcityGreenAgain, ignite-3
> Attachments: _Integration_Tests_Integration_Raft_19113.log
>
>
> {code:java}
> org.opentest4j.AssertionFailedError: expected: <true> but was: <false> at
> app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
> at app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36) at
> app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31) at
> app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:183) at
> app//org.apache.ignite.raft.jraft.core.TestCluster.ensureSame(TestCluster.java:558)
> at
> app//org.apache.ignite.raft.jraft.core.TestCluster.ensureSame(TestCluster.java:530)
> at
> app//org.apache.ignite.raft.jraft.core.ItNodeTest.testLeaderFail(ItNodeTest.java:1762)
> {code}
> This is probably caused by instability of the physical topology. In the logs
> (in attachments) we can see extra Node joined events along with suspicious
> Topology snapshot records that on its own causes following
> {code:java}
> default:int_tlf_5003:[email protected]:5003][2d796c8e-d25f-40fa-8243-db2708cdab75]
> Timeout getting GetMetadataResp from 127.0.1.1:5005 within 1000 ms, cause:
> java.util.concurrent.TimeoutException: Did not observe any item or terminal
> signal within 1000ms in 'source(MonoDefer)' (and no fallback has been
> configured)
> [01:34:25]W: [:ignite-raft:integrationTest]
> [2025-11-03T23:34:25,369][WARN ][sc-cluster-5003-447][MembershipProtocol]
> [default:int_tlf_5003:[email protected]:5003][updateMembership][SYNC]
> Skipping to add/update member: {m:
> default:int_tlf_5005:[email protected]:5005, s: ALIVE, inc: 0}, due
> to failed fetchMetadata call (cause: java.util.concurrent.TimeoutException:
> Did not observe any item or terminal signal within 1000ms in
> 'source(MonoDefer)' (and no fallback has been configured)) {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)