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.

Sign up for GitHub

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

Jump to bottom

Feature: Improve locking mechanism for active memtables #9

Open
TheIllusionistMirage opened this issue Jul 11, 2021 · 0 comments
Open

Feature: Improve locking mechanism for active memtables #9

TheIllusionistMirage opened this issue Jul 11, 2021 · 0 comments
Assignees
@TheIllusionistMirage
Labels
feature A new feature task
Projects
Sukuna Backlog

Comments

@TheIllusionistMirage
Copy link
Owner

Currently a re-entrant read-write lock is used for returning read only copies of the active memtables when using them in places like memtable to SSTable conversion. The current mechanism does not actually prevent multi-threading issues and hence has to be properly understood and re-implemented.
@TheIllusionistMirage TheIllusionistMirage self-assigned this Jul 11, 2021
@TheIllusionistMirage TheIllusionistMirage added the feature A new feature task label Jul 11, 2021
@TheIllusionistMirage TheIllusionistMirage added this to To-do in Sukuna Backlog via automation Jul 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TheIllusionistMirage TheIllusionistMirage

Labels
feature A new feature task
Projects
Sukuna Backlog
To-do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TheIllusionistMirage