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

Dataflow Locks #162

Open

4 tasks

KinanBab opened this issue Apr 17, 2023 · 0 comments

Labels

Collaborator

KinanBab commented Apr 17, 2023

Dataflow parallelism may be superflous
Improve locks: a flow-wide lock for writers only, a reader-writer lock for matview
Fork Rocksdb and provide a commit that keeps locks unreleased.
Use fork to update dataflow while holding DB locks, then release everything together.

Forking Rocksdb:

Remove the Clear() call from Commit() function in rocksdb/utilities/pessimistic_transaction.cc. Consider using a flag to disable/enable calling clear.
Expose Clear() so that we can call it manually from Pelton after committing. Consider using destructor or rollback.
Test via logging / monitoring of locks.
Open issue/PR?

KinanBab added the Futuristic label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment