This repository has been archived by the owner on Jun 23, 2022. It is now read-only.
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.
As is well known, it's not reliable enough for most replication protocols that a table has only one replica, or just two replicas. However, considering the cost, some of our customers choose to set single replica, or double replicas for a table.
In fact, PacificA Protocol can support single replica or double replicas well. Therefore, to support single replica, we can just eliminate the restriction while creating a table.
On the other hand, as described in apache/incubator-pegasus#820, now
greedy_load_balancer
cannot support single replica or double replicas well, since if a cluster has only one replica server, or two replica servers, meta server will core dump. By this PR, meta server will run normally when a cluster a cluster has one or two replica servers, especially whenmin_live_node_count_for_unfreeze
is set to 1.