Skip to content
This repository has been archived by the owner on Jun 23, 2022. It is now read-only.

feat(update_replication_factor#8): recover uncompleted update of replication factor during initialization of meta service #1110

Merged

Conversation

empiredan
Copy link
Contributor

@empiredan empiredan commented May 25, 2022

This is a subtask of apache/incubator-pegasus#865.

Since in #1087 we've supported to set env for the replication factor in case there are duplicate requests trying to update the same table, there is still a problem that the request for updating replication factor may fail once meta server crashes. It's possible that there are partial steps finished while others are uncompleted.

Therefore, After meta server has got primary lock, it will initialize, during which recovering replication factor should be relaunched. Any table whose env of updating replication factor is not removed (once updating replication factor is complete, the env will be eliminated) will be the candidate that needs to recover as long as it's available. All tables should have been restored before the initialization is finished.

empiredan added 5 commits May 24, 2022 20:23
…ication factor during initialization of meta service
…ication factor during initialization of meta service
…ication factor during initialization of meta service
…ication factor during initialization of meta service
…ication factor during initialization of meta service
src/meta/server_state.cpp Outdated Show resolved Hide resolved
src/meta/server_state.cpp Outdated Show resolved Hide resolved
src/meta/server_state.cpp Show resolved Hide resolved
…ication factor during initialization of meta service
@hycdong hycdong merged commit e75e624 into XiaoMi:max_replica_count_dev Jun 1, 2022
acelyc111 pushed a commit that referenced this pull request Jun 1, 2022
…ication factor during initialization of meta service (#1110)
acelyc111 pushed a commit that referenced this pull request Jun 6, 2022
…ication factor during initialization of meta service (#1110)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants