test: vnode count chaos test in e2e madsim #19250
Merged
+117
−16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BugenZhao
force-pushed
the
bz/vnode-count-chaos-test
branch
from
767b7a6 to
10ce155
Compare
BugenZhao
changed the base branch from
main
to
bz/scheduler-refine-for-var-vnode-count
This stack of pull requests is managed by Graphite. Learn more about stacking. |
4 tasks
BugenZhao
force-pushed
the
bz/scheduler-refine-for-var-vnode-count
branch
from
90ddcfc to
289d0cb
Compare
BugenZhao
force-pushed
the
bz/vnode-count-chaos-test
branch
8 times, most recently
from
fba9108 to
ac80a0f
Compare
BugenZhao
force-pushed
the
bz/vnode-count-chaos-test
branch
from
e9e4483 to
c6edb30
Compare
BugenZhao
force-pushed
the
bz/scheduler-refine-for-var-vnode-count
branch
from
c3f6718 to
8a5a086
Compare
BugenZhao
force-pushed
the
bz/vnode-count-chaos-test
branch
3 times, most recently
from
17276bb to
16eecea
Compare
BugenZhao
changed the title
yezizp2012
approved these changes
Nov 7, 2024
kwannoel
approved these changes
Nov 8, 2024
BugenZhao
force-pushed
the
bz/vnode-count-chaos-test
branch
from
a00787e to
0b40c9f
Compare
BugenZhao
changed the base branch from
main
to
bz/project-set-error-fix-again
4 tasks
BugenZhao
force-pushed
the
bz/vnode-count-chaos-test
branch
2 times, most recently
from
0770958 to
d4639f3
Compare
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
This reverts commit c6edb30.
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
BugenZhao
force-pushed
the
bz/project-set-error-fix-again
branch
from
1e85b92 to
be37009
Compare
BugenZhao
force-pushed
the
bz/vnode-count-chaos-test
branch
from
d4639f3 to
45ee311
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Introduce a new CLI arg
--random-vnode-countfor madsim e2e tests, which sets theSTREAMING_MAX_PARALLELISMto a random value before running each DDL statement.This covers the behavior of multiple jobs with varying vnode counts within a single cluster, especially when they have dependencies in the streaming graph.
Added as a new step in main-cron.
An example of passed run in PR workflow: https://buildkite.com/risingwavelabs/pull-request/builds/61753#01930563-f129-4363-9599-7b25af97510a
Checklist
./risedev check(or alias,./risedev c)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.