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

More granular locking mechanism #14

Open

hanappe opened this issue May 10, 2020 · 0 comments

Assignees

Labels

Contributor

hanappe commented May 10, 2020

Currently there is a single, global lock for the database. This makes it impossible to use the database on a shared, remote filesystem.

Suggestion:

Use a database lock for the creation and deletion of a scan.
Use a lock per scan for the creation/deletion of a fileset & fileset metadata
Possibly, but not urgent: Use a lock per fileset for the creation/deletion of a file & file metadata

hanappe added the enhancement label

hanappe added this to the future milestone

hanappe assigned naittaleb and hanappe

naittaleb removed this from the future milestone

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