[
https://issues.apache.org/jira/browse/IGNITE-27828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18058139#comment-18058139
]
Roman Puchkovskiy edited comment on IGNITE-27828 at 2/12/26 1:27 PM:
---------------------------------------------------------------------
The patch looks good to me
was (Author: rpuch):
The patch looks good to mme
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{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)
