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

Make logical sets of storage changes transactional #372

Open
kellpossible opened this issue Sep 2, 2021 · 1 comment
Open

Make logical sets of storage changes transactional #372

kellpossible opened this issue Sep 2, 2021 · 1 comment
Labels
bug Something isn't working refactor Changes which affect the maintainability of the code

Comments

@kellpossible
Copy link

kellpossible commented Sep 2, 2021

At the moment, we have logical sets of changes to the storage which can fail halfway, and leave the file system in an indeterminate/incorrect state which is difficult to recover from. It would be good if we can ensure that these changes can be treated as a transaction that must succeed, otherwise all changes will be reversed, leaving the file system in its original state before the transaction was attempted.

@kellpossible kellpossible added bug Something isn't working refactor Changes which affect the maintainability of the code labels Sep 2, 2021
@kellpossible
Copy link
Author

Libraries that look interesting could perhaps be used or inspiration for solving this:

Switching to Sqlite or RocksDB for storage has been suggested before, this could be an additional point in their favour.

@kellpossible kellpossible changed the title Make logical sets of file system changes transactional Make logical sets of storage changes transactional Sep 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working refactor Changes which affect the maintainability of the code
Projects
None yet
Development

No branches or pull requests

1 participant