ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #rocksdb
Learn how to tune RocksDB's WAL sync behavior to improve write throughput while understanding the durability window you may lose.
Learn how to configure RocksDB column families to give different workloads their own memtable, write buffer, and compaction settings while sharing a single DB instance.
Determine whether RocksDB's internal retry loop for WriteBatch operations guarantees that no duplicate writes are persisted to the WAL or applied to the memtable when a write stall (e.g., memtable full) triggers a retry. Assume default WAL enabled, sequence numbers are incremented on each retry, and recovery replays only the highest sequence number per key.
RocksDB utilizes WriteBatch to ensure atomicity, ensuring that a group of operations is applied as a single unit. While this prevents partial updates, the system relies on the Write-Ahead Log (WAL) for durability and recovery after a crash. A design uncertainty exists regarding the interaction between the WAL and the memtable during recovery. Specifically, i
RocksDB performs format upgrades lazily on open when a newer library version implies a newer on-disk layout. The upgrade rewrites MANIFEST and SST metadata rather than requiring an explicit upgrade command, and the change is effectively one-way. Once the MANIFEST is rewritten for a newer format, older RocksDB binaries typically cannot open the database, so d
Goal: Identify a safe combination of write_buffer_size and max_write_buffer_number that avoids write stalls or out‑of‑memory kills on production nodes with limited RAM while maintaining ingest throughput. Constraints: Production machines may have less memory than developer workstations, max_background_compactions can be limited to reduce CPU usage, and the s
When configuring RocksDB, the write stall mechanism is designed to pause writes when memory pressure from mutable memtables exceeds configured limits. The documentation states that a stall occurs if the total memory used by all mutable memtables surpasses write_buffer_limit or if the number of immutable memtables awaiting flush reaches max_write_buffer_numbe
Forward Compatibility Constraints \n RocksDB ensures that newer versions can read SST files created by older versions. However, forward compatibility is not guaranteed. When a database is upgraded to a newer version, the engine may rewrite SST files during compaction or ingestion using a more recent on-disk format version embedded in the file footer. \n If a