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

Index Crash Recovery to not overwrite blks which could be repaired in future #374

Open
hkadayam opened this issue Apr 9, 2024 · 0 comments
Assignees
Milestone

Comments

@hkadayam
Copy link
Collaborator

hkadayam commented Apr 9, 2024

There is a scenario where repair of btree nodes can be called much later than recovery (or even within recovery order is not guaranteed between 2 subtrees). As a result the repair of node branch could create new nodes which might overwrite the new node which is needed for other subtree repair (since blkid allocation is persisted only after entire flush is completed)

@hkadayam hkadayam added this to the MileStone4.2 milestone Apr 9, 2024
@hkadayam hkadayam self-assigned this Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant