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

Consider use copyset to enhance data safety. #882

Open
disksing opened this issue Dec 13, 2017 · 0 comments
Open

Consider use copyset to enhance data safety. #882

disksing opened this issue Dec 13, 2017 · 0 comments
Labels
component/schedule Scheduling logic. epic/co-availability relative availability. status/discussion-wanted The issue needs to be discussed.

Comments

@disksing
Copy link
Contributor

The main idea is to split stores into different replication groups, called 'copyset'. When we calculate the placement of a region, we choose stores belong to a same copyset.

There are some issues need to consider, such as balance between copysets, change of the number of replica.
@disksing disksing added the status/discussion-wanted The issue needs to be discussed. label Dec 13, 2017
@nolouch nolouch added component/schedule Scheduling logic. epic/co-availability relative availability. labels Jun 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/schedule Scheduling logic. epic/co-availability relative availability. status/discussion-wanted The issue needs to be discussed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nolouch @disksing