Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Why is it necessary to execute the add command first and then start the node when adding a new node to etcd #19087

Closed
4 tasks
smallemployees opened this issue Dec 19, 2024 · 0 comments
Labels

Comments

@smallemployees
Copy link

Bug report criteria

What happened?

After starting the node and executing the add command, the node cannot join the cluster

What did you expect to happen?

I want to understand the mechanism of this area, because if the operation is reversed, it cannot proceed normally

How can we reproduce it (as minimally and precisely as possible)?

I want to understand the mechanism of this area, because if the operation is reversed, it cannot proceed normally

Anything else we need to know?

No response

Etcd version (please run commands below)

$ etcd --version
# paste output here
3.5.4
$ etcdctl version
# paste output here

Etcd configuration (command line flags or environment variables)

paste your configuration here

Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)

$ etcdctl member list -w table
# paste output here

$ etcdctl --endpoints=<member list> endpoint status -w table
# paste output here

Relevant log output

No response

@etcd-io etcd-io locked and limited conversation to collaborators Dec 19, 2024
@serathius serathius converted this issue into discussion #19090 Dec 19, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Development

No branches or pull requests

1 participant