-
Notifications
You must be signed in to change notification settings - Fork 641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: more precise and reliable way to force new leaders in tests #10066
Conversation
This commit changes two things: 1. after promoting a new leader, we assert that the new leader is as expected 2. retries the promote request to allow for temporary failures, for example unavailable receivers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @oleschoenburg I have some comment see below, please check them before merging :)
.getServer(); | ||
|
||
Awaitility.await("Promote request is successful") | ||
.pollInterval(Duration.ofMillis(500)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❓ Any specifc reason for that poll interval?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not at all, 500ms just felt like a reasonable interval before retrying 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm ok I would just remove it, otherwise it looks like it is important 🤷
qa/integration-tests/src/test/java/io/camunda/zeebe/it/clustering/ReaderCloseTest.java
Outdated
Show resolved
Hide resolved
Thanks @Zelldon! bors r+ |
10066: fix: more precise and reliable way to force new leaders in tests r=oleschoenburg a=oleschoenburg ## Description This PR changes two things: 1. after promoting a new leader, we assert that the new leader is as expected 2. retries the promote request to allow for temporary failures, for example unavailable receivers ## Related issues <!-- Which issues are closed by this PR or are related --> closes #9921 Co-authored-by: Ole Schönburg <[email protected]>
Build failed: |
bors retry |
Build succeeded: |
Flaky on stable/8.0 still. Let me try backporting /backport |
Successfully created backport PR for |
13453: [Backport stable/8.0] Limit error message size in job and incident records r=remcowesterhoud a=nicpuppa backport #12066 relates to #11460 13455: [Backport stable/8.0] fix: more precise and reliable way to force new leaders in tests r=remcowesterhoud a=backport-action # Description Backport of #10066 to `stable/8.0`. relates to #9921 Co-authored-by: camunda\berkay.can <[email protected]> Co-authored-by: Ole Schönburg <[email protected]>
Description
This PR changes two things:
Related issues
closes #9921
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
backport stable/1.3
) to the PR, in case that fails you need to create backports manually.Testing:
Documentation:
Please refer to our review guidelines.