Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support configuring initial-cluster-token #2689

Closed
disksing opened this issue Jul 29, 2020 · 0 comments · Fixed by #2691
Closed

Support configuring initial-cluster-token #2689

disksing opened this issue Jul 29, 2020 · 0 comments · Fixed by #2691
Assignees
@disksing
Labels
type/enhancement The issue or PR belongs to an enhancement.

Comments

@disksing
Copy link
Contributor

Development Task

The cluster ID of etcd is generated by configuration, which means from the same configuration we will get same cluster id. It can cause problems when destroy and re-deploy with the same config. #2606 is a good example.

We can expose initial-cluster-token as a PD config to distinguish different clusters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@disksing disksing

Labels
type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

config: add initial-cluster-token config oh-my-tidb/pd
1 participant
@disksing