aleksraiden opened a new pull request, #2694: URL: https://github.com/apache/kvrocks/pull/2694
Bump rocksdb to v9.9.3 - full changelog: https://github.com/facebook/rocksdb/releases/tag/v9.9.3 **Key features** - In buffered IO mode, try to align writes on power of 2 if checksum handoff is not enabled for the file type being written - Adds a new table property "rocksdb.newest.key.time" which records the unix timestamp of the newest key. Uses this table property for FIFO TTL and temperature change compaction - Added a new API Transaction::GetAttributeGroupIterator that can be used to create a multi-column-family attribute group iterator over the specified column families, including the data from both the transaction and the underlying database. - Added a new API Transaction::GetCoalescingIterator that can be used to create a multi-column-family coalescing iterator over the specified column families, including the data from both the transaction and the underlying database - Fix a leak of obsolete blob files left open until DB::Close(). This bug was introduced in version 9.4.0. - Fix missing cases of corruption retry during DB open and read API processing - Fix a bug for transaction db with 2pc where an old WAL may be retained longer than needed - Fix leaks of some open SST files (until DB::Close()) that are written but never become live due to various failures. (We now have a check for such leaks with no outstanding issues.) - Fix a bug for replaying WALs for WriteCommitted transaction DB when its user-defined timestamps setting is toggled on/off between DB sessions. - Fix regression in issue https://github.com/facebook/rocksdb/issues/12038 due to Options::compaction_readahead_size greater than max_sectors_kb (i.e, largest I/O size that the OS issues to a block device defined in linux) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
