This repository has been archived by the owner on Feb 6, 2024. It is now read-only.
refactor: implement failover based distributed etcd lock #146
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8eb2463 to
d8c531c
Compare
1948994 to
f8b75dc
Compare
ShiKaiWi
reviewed
Mar 29, 2023
ShiKaiWi
reviewed
Mar 29, 2023
ShiKaiWi
reviewed
Mar 30, 2023
e25d281 to
5914044
Compare
ShiKaiWi
reviewed
Mar 30, 2023
2ac676b to
6b93887
Compare
ShiKaiWi
approved these changes
Mar 30, 2023
ZuLiangWang
added a commit
to ZuLiangWang/ceresmeta
that referenced
this pull request
Apr 12, 2023
ShiKaiWi
pushed a commit
that referenced
this pull request
Apr 20, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
(#145)
Rationale for this change
In order to ensure that user data in distributed mode will not be lost, we need a mechanism to ensure that CeresDB will not have multiple leader shard under any circumstances.
etcdlock has been added in apache/horaedb#706 , we refactor scheduler to implement failover basedetcddistributed lock.What changes are included in this PR?
Are there any user-facing changes?
None.
How does this change test
Pass all unit tests and integration tests.