[IGNITE-15036] ITNodeTest.testLeaderStopAndReElectWithPriority is flaky

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha2
• Fix Version/s: 3.0.0-alpha3
• Labels: ignite-3
• Assignee: Vladislav Pyatkov
• Reporter: Alexey Scherbakov
• Created: 30/Jun/21 12:48
• Updated: 21/Jul/21 14:14
• Resolved: 21/Jul/21 14:14

Description

https://ci.ignite.apache.org/viewLog.html?buildId=6066429&buildTypeId=ignite3_Test_IntegrationTests_IntegrationTests

https://ci.ignite.apache.org/viewLog.html?buildId=6070466&buildTypeId=ignite3_Test_RunAllTests

This test was written incorrectly, because it waits that a node which was elected as a leader has to have the longest log, if it has less priority than another.
But it is a truth only a moment when the node was elected as a leader, and any moment after that, the other node may catch up the leader.
Need to wait when all nodes will have same log size, that makes a leader election predictable (it will depend on priority).

Issue Links

• is part of: IGNITE-14832 Investigate remaining TODOs in org.apache.ignite.raft.jraft package
• links to: GitHub Pull Request #231