timoninmaxim commented on a change in pull request #9529:
URL: https://github.com/apache/ignite/pull/9529#discussion_r744224111
##########
File path:
modules/control-utility/src/test/java/org/apache/ignite/util/KillCommandsCommandShTest.java
##########
@@ -271,16 +287,25 @@ public void testCancelConsistencyTask() throws
InterruptedException {
thLatch.countDown();
});
+ // GridNearGetRequest messages count required to pefrom getAll() with
readRepair from all nodes twice.
+ // First will be finished (which generates status), second will be
frozen.
+ int twiceGetMsgCnt = SERVER_NODE_CNT * (SERVER_NODE_CNT - 1) * 2;
Review comment:
Looks like this test can be simplified. If the consistency status map
will be notified on the repair task just started then we can wait just
"0/10000" instead of "1024/10000". So, there is no need to implement complex
logic for waiting specific events? WDYT?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
