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

Handling tail-corrupted entry in remote WAL #4069

Open
WenyXu opened this issue May 29, 2024 · 0 comments
Open

Handling tail-corrupted entry in remote WAL #4069

WenyXu opened this issue May 29, 2024 · 0 comments
Labels
C-enhancement Category Enhancements

Comments

@WenyXu
Copy link
Member

WenyXu commented May 29, 2024

What type of enhancement is this?

Tech debt reduction

What does the enhancement do?

By default, we only tolerate tail-corrupted entry in remote WAL. However, we should trigger a flush once the region leader detects the tail corrupted entry during the replay(updates the last_flushed_entry_id in the manifest).

image
(Figure: tail-corrupted data in remote WAL)

Implementation challenges

No response

@WenyXu WenyXu added the C-enhancement Category Enhancements label May 29, 2024
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

No branches or pull requests

1 participant