Skip to content

IGNITE-23708 testAutomaticRebalanceIfMajorityIsLost is flaky#4747

Merged
sanpwc merged 5 commits intoapache:mainfrom
gridgain:ignite-23708
Nov 22, 2024
Merged

IGNITE-23708 testAutomaticRebalanceIfMajorityIsLost is flaky#4747
sanpwc merged 5 commits intoapache:mainfrom
gridgain:ignite-23708

Conversation

@JAkutenshi
Copy link
Copy Markdown
Contributor

JIRA Ticket: IGNITE-23708

The goal

The main goal of the PR is to fix testAutomaticRebalanceIfMajorityIsLost:

  1. Reset rebalance may be slower a little than expected 2s timeout on assertRealAssignments(node0, partId, 1) especially after IGNITE-22036 changes.
  2. There is unnecessary planned rebalance with the same planned assignments as pending force reset assignments set equals to [1]. This leads also to a flacky non-null result on assertNull(getPendingAssignments(node0, partId)) check.

The reason

Tests shouldn't be flacky and flawed implementation should be fixed.

The solution

  1. assertRealAssignments's timeout is increased up to 5s.
  2. If during GroupUpdateRequest#partitionUpdate if there are alive nodes we have equal part and stable assignments we shouldn't schedule the redundant rebalance and then should put just null then.

@sanpwc sanpwc changed the title IGNITE-23708 testAutomaticRebalanceIfMajorityIsLost is flacky IGNITE-23708 testAutomaticRebalanceIfMajorityIsLost is flaky Nov 19, 2024
# Conflicts:
#	modules/table/src/main/java/org/apache/ignite/internal/table/distributed/disaster/GroupUpdateRequest.java
@sanpwc sanpwc merged commit 39749ad into apache:main Nov 22, 2024
@sanpwc sanpwc deleted the ignite-23708 branch November 22, 2024 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants