-
Notifications
You must be signed in to change notification settings - Fork 37
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
Drop BoltDB from write cache #3076
Labels
enhancement
Improving existing functionality
I4
No visible changes
neofs-storage
Storage node application issues
performance
More of something per second
S3
Minimally significant
U2
Seriously planned
Milestone
Comments
This was referenced Dec 28, 2024
End-rey
added a commit
that referenced
this issue
Jan 27, 2025
Previously, the write-cache has 2 components: bolt database and fstree. BoltDB is absolutely useless for write caching given that the cache uses SSD, so it was decided to drop this database. Drop all code related to BoltDB. Migrate from this database to the main storage, by flushing objects. Remove config parameters for the write-cache: `small_object_size`, `workers_number`, `max_batch_delay`, `max_batch_size`. Update docs. Rewrite lens commands for the current version of the write-cache. Closes #3076. Signed-off-by: Andrey Butusov <[email protected]>
End-rey
added a commit
that referenced
this issue
Jan 28, 2025
Previously, the write-cache has 2 components: bolt database and fstree. BoltDB is absolutely useless for write caching given that the cache uses SSD, so it was decided to drop this database. Drop all code related to BoltDB. Migrate from this database to the main storage, by flushing objects. Remove config parameters for the write-cache: `small_object_size`, `workers_number`, `max_batch_delay`, `max_batch_size`. Update docs. Rewrite lens commands for the current version of the write-cache. Closes #3076. Signed-off-by: Andrey Butusov <[email protected]>
End-rey
added a commit
that referenced
this issue
Jan 28, 2025
Previously, the write-cache has 2 components: bolt database and fstree. BoltDB is absolutely useless for write caching given that the cache uses SSD, so it was decided to drop this database. Drop all code related to BoltDB. Migrate from this database to the main storage, by flushing objects. Remove config parameters for the write-cache: `small_object_size`, `workers_number`, `max_batch_delay`, `max_batch_size`. Update docs. Rewrite lens commands for the current version of the write-cache. Closes #3076. Signed-off-by: Andrey Butusov <[email protected]>
roman-khimov
added a commit
that referenced
this issue
Jan 30, 2025
End-rey
added a commit
that referenced
this issue
Jan 31, 2025
Refs #3076. Signed-off-by: Andrey Butusov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
Improving existing functionality
I4
No visible changes
neofs-storage
Storage node application issues
performance
More of something per second
S3
Minimally significant
U2
Seriously planned
Is your feature request related to a problem? Please describe.
I'm always frustrated when we have something we don't need. BoltDB is absolutely useless for write caching given that the cache uses SSD (see #2337 (comment) also).
Describe the solution you'd like
Drop it from the structure completely. Provide migration, flush all objects from it to the storage and then forever drop the DB, don't use it for object storage.
The text was updated successfully, but these errors were encountered: