You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 6, 2024. It is now read-only.
## Rationale
In some extreme cases (for this situation, please refer to
#296), the shard
node cannot be cleaned normally, and we need to add an operation and
maintenance interface to complete manual cleaning.
## Detailed Changes
* Add drop shard node api.
## Test Plan
Pass CI.
## Rationale
In some extreme cases (for this situation, please refer to
apache#296), the shard
node cannot be cleaned normally, and we need to add an operation and
maintenance interface to complete manual cleaning.
## Detailed Changes
* Add drop shard node api.
## Test Plan
Pass CI.
## Rationale
In some extreme cases (for this situation, please refer to
#296), the shard
node cannot be cleaned normally, and we need to add an operation and
maintenance interface to complete manual cleaning.
## Detailed Changes
* Add drop shard node api.
## Test Plan
Pass CI.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe this problem
We found that the failover mechanism of the HoraeDB cluster failed, and the shard was not migrated when the machine went down.
Steps to reproduce
Additional Information
ShardNode
api to deal with some extreme situations.The text was updated successfully, but these errors were encountered: