-
Notifications
You must be signed in to change notification settings - Fork 332
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: add '--store-key-prefix' to support multiple meta instances can use the same etcd backend #2988
feat: add '--store-key-prefix' to support multiple meta instances can use the same etcd backend #2988
Conversation
a0a1844
to
a7741aa
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #2988 +/- ##
===========================================
- Coverage 85.87% 85.28% -0.60%
===========================================
Files 780 780
Lines 126184 126248 +64
===========================================
- Hits 108356 107666 -690
- Misses 17828 18582 +754 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest LGTM
… use the same etcd backend
a7741aa
to
5f0d5cf
Compare
Question: it this parameter only be passed by the command line arg? Can the users configure it in |
Oh, it seems that it cannot be configured through the toml file, I think we need a way with toml. @zyy17 |
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
When deploying multiple clusters, it's more convenient and cost-effective to re-use the same etcd cluster.
In this PR, I added
--store-key-prefix
which is specified by the admin in the metasrv to support that multiple metasrv instances can use the same etcd cluster without key confliction.Checklist
Refer to a related PR or issue link (optional)