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.

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

tolerate 2 replicas failure with 3 data replicas #17943

Open
hicqu opened this issue Jun 11, 2020 · 1 comment
Open

tolerate 2 replicas failure with 3 data replicas #17943

hicqu opened this issue Jun 11, 2020 · 1 comment
Assignees
Labels
feature/reviewing This feature request is reviewing by product managers type/feature-request Categorizes issue or PR as related to a new feature.

Comments

@hicqu
Copy link
Contributor

hicqu commented Jun 11, 2020

Feature Request

Currently if we want to tolerate 2 replicas failure, TiDB clusters need to be deployed with 5 data replicas. It's too expensive for some users. However, some other databases can use only 3 data replicas to reach this. Support this feature can make TiDB be better than them.

Is your feature request related to a problem? Please describe:

Describe the feature you'd like:

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

We can image that mainly changes about the feature will be in TiKV, especially component Raft.
And there are some articles described the same problem, and tried to resolve it. One solution is based on Witness, a new role in Raft.

@hicqu hicqu added the type/feature-request Categorizes issue or PR as related to a new feature. label Jun 11, 2020
@zhangjinpeng87
Copy link
Contributor

How to provide service when 2 replicas failed?

@zz-jason zz-jason added the feature/reviewing This feature request is reviewing by product managers label Aug 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/reviewing This feature request is reviewing by product managers type/feature-request Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants