[
https://issues.apache.org/jira/browse/IGNITE-19996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-19996:
---------------------------------
Description:
{{ItNodeTest#testNewPeersConfigurationAppliedListener}} started to fail time to
time with
{noformat}
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:180)
at
app//org.apache.ignite.raft.jraft.core.ItNodeTest.testNewPeersConfigurationAppliedListener(ItNodeTest.java:3038)
{noformat}
Brief investigation showed, that logs are full of
{noformat}
2023-07-18 12:50:39:922 +0400
[DEBUG][int_tnpcal_5006-client-6][HandshakeHandler] Error when performing
handshake
org.apache.ignite.internal.network.handshake.ChannelAlreadyExistsException
at
org.apache.ignite.internal.network.recovery.RecoveryClientHandshakeManager.onHandshakeStartMessage(RecoveryClientHandshakeManager.java:235)
at
org.apache.ignite.internal.network.recovery.RecoveryClientHandshakeManager.onMessage(RecoveryClientHandshakeManager.java:151)
at
org.apache.ignite.internal.network.netty.HandshakeHandler.channelRead(HandshakeHandler.java:92)
{noformat}
and
{noformat}
2023-07-18 12:50:38:896 +0400
[DEBUG][int_tnpcal_5003-srv-worker-2][HandshakeHandler] Error when performing
handshake
java.io.IOException: Connection reset by peer
{noformat}
Seems that sometimes it is impossible to perform {{changePeers}} from the test
because we see this errors right after we try to perform this action:
{noformat}
2023-07-18 12:50:39:710 +0400 [ERROR][Test worker][AbstractClientService] Fail
to connect int_tnpcal_5006, exception: java.net.ConnectException.
2023-07-18 12:50:39:710 +0400 [ERROR][Test worker][ReplicatorGroupImpl] Fail to
check replicator connection to peer=int_tnpcal_5006, replicatorType=Follower.
2023-07-18 12:50:39:710 +0400 [ERROR][Test worker][NodeImpl] Node
<testChangePeers/int_tnpcal_5005> start the replicator failed,
peer=int_tnpcal_5006.
{noformat}
and
{noformat}
2023-07-18 12:50:39:921 +0400
[INFO][int_tnpcal_5006-client-6][RecoveryClientHandshakeManager] Failed to
acquire recovery descriptor during handshake, it is held by: [id: 0x33e12310,
L:/127.0.0.1:5006 - R:/127.0.0.1:64991]
{noformat}
Seems that IGNITE-19903 has brought the problems.
> ItNodeTest#testNewPeersConfigurationAppliedListener become flaky
> ----------------------------------------------------------------
>
> Key: IGNITE-19996
> URL: https://issues.apache.org/jira/browse/IGNITE-19996
> Project: Ignite
> Issue Type: Bug
> Reporter: Mirza Aliev
> Priority: Major
> Labels: ignite-3
>
> {{ItNodeTest#testNewPeersConfigurationAppliedListener}} started to fail time
> to time with
> {noformat}
> 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:180)
> at
> app//org.apache.ignite.raft.jraft.core.ItNodeTest.testNewPeersConfigurationAppliedListener(ItNodeTest.java:3038)
> {noformat}
> Brief investigation showed, that logs are full of
> {noformat}
> 2023-07-18 12:50:39:922 +0400
> [DEBUG][int_tnpcal_5006-client-6][HandshakeHandler] Error when performing
> handshake
> org.apache.ignite.internal.network.handshake.ChannelAlreadyExistsException
> at
> org.apache.ignite.internal.network.recovery.RecoveryClientHandshakeManager.onHandshakeStartMessage(RecoveryClientHandshakeManager.java:235)
> at
> org.apache.ignite.internal.network.recovery.RecoveryClientHandshakeManager.onMessage(RecoveryClientHandshakeManager.java:151)
> at
> org.apache.ignite.internal.network.netty.HandshakeHandler.channelRead(HandshakeHandler.java:92)
> {noformat}
> and
> {noformat}
> 2023-07-18 12:50:38:896 +0400
> [DEBUG][int_tnpcal_5003-srv-worker-2][HandshakeHandler] Error when performing
> handshake
> java.io.IOException: Connection reset by peer
> {noformat}
> Seems that sometimes it is impossible to perform {{changePeers}} from the
> test because we see this errors right after we try to perform this action:
> {noformat}
> 2023-07-18 12:50:39:710 +0400 [ERROR][Test worker][AbstractClientService]
> Fail to connect int_tnpcal_5006, exception: java.net.ConnectException.
> 2023-07-18 12:50:39:710 +0400 [ERROR][Test worker][ReplicatorGroupImpl] Fail
> to check replicator connection to peer=int_tnpcal_5006,
> replicatorType=Follower.
> 2023-07-18 12:50:39:710 +0400 [ERROR][Test worker][NodeImpl] Node
> <testChangePeers/int_tnpcal_5005> start the replicator failed,
> peer=int_tnpcal_5006.
> {noformat}
> and
> {noformat}
> 2023-07-18 12:50:39:921 +0400
> [INFO][int_tnpcal_5006-client-6][RecoveryClientHandshakeManager] Failed to
> acquire recovery descriptor during handshake, it is held by: [id: 0x33e12310,
> L:/127.0.0.1:5006 - R:/127.0.0.1:64991]
> {noformat}
> Seems that IGNITE-19903 has brought the problems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
