Fix issue with RocksDB producing tiny SST files 3.12.6 #22182
+7
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kvahed
added
3 RocksDB
kvahed
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Scope & Purpose
Prevent RocksDB from creating tiny SST files for large number of databases, collections
Checklist
Related Information
(Please reference tickets / specification / other PRs etc)
Note
Turns off default partitioning of document column family SST files and updates the changelog with a fix note.
arangod/RocksDBEngine/RocksDBOptionFeature.cpp: set_partitionFilesForDocumentsCftofalse(stop partitioning document data into per-collection/shard.sstfiles by default).3.12.6.2entry noting fix for RocksDB creating tiny.sstfiles.Written by Cursor Bugbot for commit 55672cf. This will update automatically on new commits. Configure here.