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

chore: Bump rocksdb to v9.7.2 #2600

Merged
merged 2 commits into from
Oct 17, 2024
Merged

chore: Bump rocksdb to v9.7.2 #2600

merged 2 commits into from
Oct 17, 2024

Conversation

aleksraiden
Copy link
Contributor

@aleksraiden aleksraiden commented Oct 14, 2024

Bump rocksdb to v9.7.2, first public release of 9.7.x. Full changelog - https://github.com/facebook/rocksdb/releases/tag/v9.7.2

Key features

  • Set write_dbid_to_manifest=true by default. This means DB ID will now be preserved through backups, checkpoints, etc. by default. Also add write_identity_file option which can be set to false for anticipated future behavior
  • Add a new table property "rocksdb.key.largest.seqno" which records the largest sequence number of all keys in file. It is verified to be zero during SST file ingestion
  • Changed the semantics of the BlobDB configuration option blob_garbage_collection_force_threshold to define a threshold for the overall garbage ratio of all blob files currently eligible for garbage collection
  • In FIFO compaction, compactions for changing file temperature (configured by option file_temperature_age_thresholds) will compact one file at a time, instead of merging multiple eligible file together
  • Support ingesting db generated files using hard link
  • DB::Close now untracks files in SstFileManager, making avaialble any space used by them. Prior to this change they would be orphaned until the DB is re-opened

Bug fixes

  • Fix a bug in CompactRange() where result files may not be compacted in any future compaction
  • Fix a bug with manual_wal_flush and auto error recovery from WAL failure that may cause CFs to be inconsistent
  • Skip insertion of compressed blocks in the secondary cache if the lowest_used_cache_tier DB option is kVolatileTier
  • Fix under counting of allocated memory in the compressed secondary cache due to looking at the compressed block size rather than the actual memory allocated, which could be larger due to internal fragmentation
  • Several DB option settings could be lost through GetOptionsFromString(), possibly elsewhere as well

Copy link

@PragmaTwice PragmaTwice merged commit 1d77232 into unstable Oct 17, 2024
61 of 62 checks passed
@PragmaTwice PragmaTwice deleted the aleksraiden-patch-1 branch October 20, 2024 14:42
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.

5 participants