You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@kvrocks.apache.org by GitBox <gi...@apache.org> on 2026/09/17 04:46:48 UTC

[GH] (kvrocks/direct-io-option): Workflow run "CI" failed!

The GitHub Actions job "CI" on kvrocks.git/direct-io-option has failed.
Run started by GitHub user bocharov (triggered by bocharov).

Head commit for run:
f879da780567fe9e07e6c1d473a4440c5341b6dd / Alexander Bocharoff <al...@epochal.com>
feat(rocksdb): add optional direct I/O for reads and flush/compaction

Add two opt-in RocksDB options, both off by default:
  rocksdb.use_direct_reads
  rocksdb.use_direct_io_for_flush_and_compaction

They map to the corresponding RocksDB DBOptions and let an operator bypass the
OS page cache. With buffered reads the page cache grows with the working set and,
under a hard memory limit (e.g. a cgroup memory limit), is accounted against that
limit and can lead to the process being OOM-killed; direct reads keep the process
memory bounded to the block cache (size it to the working set when enabling).
Both default off, so existing behavior is unchanged. They are applied when the DB
is opened, so they are read-only at runtime.

Documented in kvrocks.conf; covered by a cppunit test (defaults, file parsing,
read-only) and a gocase test (defaults + read-only via a running server).

Report URL: https://github.com/apache/kvrocks/actions/runs/32100290225

With regards,
GitHub Actions via GitBox