Skip to content

feat: make metadata update operation atomic in persisten cache storage #1593

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

Merged
merged 1 commit into from
Feb 12, 2025

Conversation

szymonmaslowski
Copy link
Contributor

Context

In order to make sure the cache metadata collection tracks properly all the stored cache items it is required for read and write operations to be performed in sequence. Otherwise, some parallel metadata writing might cause data loss.

Proposed Solution

Making read and write operations atomic by maintaining a queue of those operations and performing next one only if previous one finished.

Important Changes Introduced

Copy link
Contributor

@przemyslaw-wlodek przemyslaw-wlodek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💪🏻 🚢

@szymonmaslowski szymonmaslowski merged commit e4947c0 into master Feb 12, 2025
5 of 6 checks passed
@szymonmaslowski szymonmaslowski deleted the feat/LW-12228-improve-caching-mechanism branch February 12, 2025 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants