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

Allow different types of metadata to be stored in the data storage #245

Open
lni opened this issue Sep 26, 2021 · 0 comments
Open

Allow different types of metadata to be stored in the data storage #245

lni opened this issue Sep 26, 2021 · 0 comments
Assignees
Labels
Milestone

Comments

@lni
Copy link
Contributor

lni commented Sep 26, 2021

We currently assume that metadata is small and updated infrequently, e.g. membership info of each raft group is only updated when requested by the prophet. For such kind of metadata, we store its serialized form into data storage using the current interface.

There are other kind of metadata that we can't afford to dump the whole set to the data storage on each update, e.g. the client_id/update_id pairs used for preventing retried requests to be applied more than once, it is updated on each write. Such data has to be incrementally updated into the data storage and we have to consider how to GC its old data.

This issue only deals with how the data storage interface should be updated to support such new metadata types.

@lni lni added kind/enhancement New feature or request component/raftstore raftstore priority/medium P3 labels Sep 26, 2021
@lni lni added this to the v0.3.0 milestone Sep 26, 2021
@lni lni modified the milestones: v0.3.0, backlog Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants