[
https://issues.apache.org/jira/browse/IGNITE-27828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtsev updated IGNITE-27828:
-----------------------------------------
Description:
{{nodeCannotCommunicateAfterLeavingPhysicalTopology}} runs the following
scenario:
# A node is "knocked out" - a network segmentation is emulated by dropping all
messages from other nodes to this node;
# We then send a message from the "knocked out" node to another node and expect
the send method to fail.
However, there exists a race, where the "knocked out" node can reuse an
existing channel to successfully send the message, because channels are closed
asynchronously and we don't wait for them to be closed in the test.
> ItScaleCubeNetworkMessagingTest#nodeCannotCommunicateAfterLeavingPhysicalTopology
> is flaky
> ------------------------------------------------------------------------------------------
>
> Key: IGNITE-27828
> URL: https://issues.apache.org/jira/browse/IGNITE-27828
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Polovtsev
> Assignee: Aleksandr Polovtsev
> Priority: Major
> Labels: MakeTeamcityGreenAgain, ignite-3
>
> {{nodeCannotCommunicateAfterLeavingPhysicalTopology}} runs the following
> scenario:
> # A node is "knocked out" - a network segmentation is emulated by dropping
> all messages from other nodes to this node;
> # We then send a message from the "knocked out" node to another node and
> expect the send method to fail.
> However, there exists a race, where the "knocked out" node can reuse an
> existing channel to successfully send the message, because channels are
> closed asynchronously and we don't wait for them to be closed in the test.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
