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

Specify the server_id explicitly to avoid possible conflict #24

Open
jd-zhang opened this issue Jun 16, 2022 · 1 comment
Open

Specify the server_id explicitly to avoid possible conflict #24

jd-zhang opened this issue Jun 16, 2022 · 1 comment
Labels
cloudnative defect @high #minor

Comments

@jd-zhang
Copy link
Contributor

Issue migrated from trac ticket # 828

component: cluster provision | priority: major

2022-06-16 15:44:13: zhangjindong@zettadb.com created the issue

Currently, when not specified, the server_id is generated by a random, this could(although possibility is low) introduce same values for nodes inside a group.

We can generate the value explicitly, to avoid the conflict, this including the following part:

  • one-key installation script
  • clustermgr setup script.
@jd-zhang
Copy link
Contributor Author

2022-06-16 15:44:20: zhangjindong@zettadb.com changed status from assigned to accepted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cloudnative defect @high #minor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jd-zhang