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

Introduce the Readonly flag in TableRouteValue #2638

Closed
WenyXu opened this issue Oct 23, 2023 · 1 comment · Fixed by #2715
Closed

Introduce the Readonly flag in TableRouteValue #2638

WenyXu opened this issue Oct 23, 2023 · 1 comment · Fixed by #2715
Labels
C-enhancement Category Enhancements
Milestone

Comments

@WenyXu
Copy link
Member

WenyXu commented Oct 23, 2023

What type of enhancement is this?

Refactor, Tech debt reduction

What does the enhancement do?

We must set the read-only flag before actions for any dead or unavailable writable region(the Leader Peer).

We currently use the InactiveRegionManager. After the old MetaServer Leader crashes, the new Leader will re-register the inactive region. However, there may be a Datanode restart and get the wrong leases before the new Leader re-registering the inactive region.
image

Implementation challenges

No response

@WenyXu WenyXu added the C-enhancement Category Enhancements label Oct 23, 2023
@WenyXu WenyXu added this to the v0.5 milestone Oct 23, 2023
@WenyXu
Copy link
Member Author

WenyXu commented Oct 23, 2023

BTW, We might also need to introduce an Initializing flag for the writable region(the Leader Peer) to help MetaServer handle the region lease properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category Enhancements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant