-
Notifications
You must be signed in to change notification settings - Fork 613
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
feat(risedev): support multiple etcd and multiple meta node #6421
Conversation
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #6421 +/- ##
==========================================
- Coverage 74.05% 74.04% -0.02%
==========================================
Files 966 972 +6
Lines 157832 158105 +273
==========================================
+ Hits 116887 117071 +184
- Misses 40945 41034 +89
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Do we want to add this setting into the e2e tests in CI? |
This looks really amazing! Thank you for this work! |
It doesn’t work at all for now |
* feat(risedev): support multiple etcd and multiple meta node Signed-off-by: Bugen Zhao <[email protected]> * fix Signed-off-by: Bugen Zhao <[email protected]> Signed-off-by: Bugen Zhao <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
What exactly does not work for you? |
My understanding is that there are indeed multiple meta nodes by triggering this setting, but they just exist and only one node has actual connection with the rest of the components in the cluster. |
That is correct. In the current setup one node will become leader and the followers will idle forever, even if the leader fails. The relevant code that halts execution can be found here: risingwave/src/meta/src/rpc/server.rs Line 269 in 3699a78
Status of HA setup We are currently working on the HA setup for meta (see tracking issue). The first draft that does failover handling can be found here #6466 The current failover handling "works": A new leader gets elected and starts its services. However, because of #6534 this node immediately crashes. |
Signed-off-by: Bugen Zhao 2 [email protected]
I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
This PR adds support for multiple etcd and multiple meta node. Use
./risedev d 3etcd-3meta-1cn-1fe
to set up this profile.Checklist
./risedev check
(or alias,./risedev c
)Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.
Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)
ref #5943
cc @CAJan93