mdcallag
commented
1 year ago From your example above, uiLsize isn't 3T, it is 1024*3T
uint64_t uiL0size = 1024 * 1024 * 1024;
uiL0size = 512 * uiL0size; //512G
uint64_t uiLsize = 1024 * 1024 * 1024;
uiLsize = 3*1024 * 1024 * uiLsize; // 3TI can't reproduce this after building from main.
rm -rf p1; rm -rf p2; mkdir p1; mkdir p2; ./db_bench --benchmarks=fillrandom,stats --num=1000000 --value_size=1000 --compression_type=none ; du -hs p1; du -hs p2 ; du -hs /tmp/rocksdbtest-2260
Output is:
628M p1
193M p2
40M /tmp/rocksdbtest-2260
diff --git a/tools/db_bench_tool.cc b/tools/db_bench_tool.cc
index 19ca1b4c0..2ac4c7842 100644
--- a/tools/db_bench_tool.cc
+++ b/tools/db_bench_tool.cc
@@ -4844,6 +4844,13 @@ class Benchmark {
FLAGS_secondary_update_interval, db));
}
} else {
+ std::cout << "Open here\n";
+ std::string p1 = "./p1";
+ std::string p2 = "./p2";
+ uint64_t s1 = 1024ULL * 1024 * 1024 * 1;
+ uint64_t s2 = 1024ULL * 1024 * 1024 * 500;
+ options.db_paths.push_back({ p1, s1 });
+ options.db_paths.push_back({ p2, s2 });
s = DB::Open(options, db_name, &db->db);
}
if (FLAGS_report_open_timing) {
gaowayne
ajkr
Expected behavior
if I configure two NVMe SSD devices with db_paths, RocksDB should start use 2nd NVMe SSD after 1st one is full.
Actual behavior
now, RocksDB report no space left error when 1st NVMe SSD is full.
Steps to reproduce the behavior
prepare two NVMe SSD, create one small partition for 1st NVMe SSD, then configure db_paths as below
[root@phobos rocksdb]# ./db_bench --num=60000000 --db=/mnt/nvme7n1p4/test1 --histogram=1 --key_size=4096 --value_size=8192 --compression_type=none --benchmarks="fillrandom,stats" --statistics --stats_per_interval=1 --stats_interval_seconds=240 --threads=1 --target_file_size_multiplier=10 --write_buffer_size=134217728 --use_existing_db=0 --disable_wal=false --cache_size=536870912 --bloom_bits=10 --bloom_locality=1 --compaction_style=0 --universal_max_size_amplification_percent=500 --max_write_buffer_number=16 --max_background_flushes=16 --level0_file_num_compaction_trigger=32 --level0_slowdown_writes_trigger=160 --level0_stop_writes_trigger=288 --soft_pending_compaction_bytes_limit=549755813888 --hard_pending_compaction_bytes_limit=1099511627776 --max_background_jobs=4 --max_background_compactions=4 --subcompactions=20