This is an automated email from the ASF dual-hosted git repository.
yunhong pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fluss.git
The following commit(s) were added to refs/heads/main by this push:
new d59fdfcc3 [doc] fix kv.snapshot.num-retained default value (#2797)
d59fdfcc3 is described below
commit d59fdfcc3b84c27f464213ac324ab2ca7b7fa127
Author: xiaozhou <[email protected]>
AuthorDate: Thu Mar 5 11:38:55 2026 +0800
[doc] fix kv.snapshot.num-retained default value (#2797)
---
website/docs/maintenance/configuration.md | 4 ++--
website/docs/maintenance/tiered-storage/remote-storage.md | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/website/docs/maintenance/configuration.md
b/website/docs/maintenance/configuration.md
index 80d40fddb..ae9116a7c 100644
--- a/website/docs/maintenance/configuration.md
+++ b/website/docs/maintenance/configuration.md
@@ -138,7 +138,7 @@ during the Fluss cluster working.
| kv.snapshot.interval | Duration | 10min
| The interval to perform periodic snapshot for kv data. The
default setting is 10 minutes.
[...]
| kv.snapshot.scheduler-thread-num | Integer | 1
| The number of threads that the server uses to schedule
snapshot kv data for all the replicas in the server.
[...]
| kv.snapshot.transfer-thread-num | Integer | 4
| **Deprecated**: This option is deprecated. Please use
`server.io-pool.size` instead. The number of threads the server uses to
transfer (download and upload) kv snapshot files.
[...]
-| kv.snapshot.num-retained | Integer | 1
| The maximum number of completed snapshots to retain.
[...]
+| kv.snapshot.num-retained | Integer | 2
| The maximum number of completed snapshots to retain.
[...]
| kv.snapshot.lease-expiration-check-interval | Duration | 10min
| The interval to check the expiration of kv snapshot leases.
The default setting is 10 minutes.
[...]
| kv.rocksdb.thread.num | Integer | 2
| The maximum number of concurrent background flush and
compaction jobs (per bucket of table). The default value is `2`.
[...]
| kv.rocksdb.files.open | Integer | -1
| The maximum number of open files (per bucket of table)
that can be used by the DB, `-1` means no limit. The default value is `-1`.
[...]
@@ -158,7 +158,7 @@ during the Fluss cluster working.
| kv.rocksdb.block.blocksize | MemorySize | 4kb
| The approximate size (in bytes) of user data packed per
block. The default blocksize is `4KB`.
[...]
| kv.rocksdb.block.cache-size | MemorySize | 8mb
| The amount of the cache for data blocks in RocksDB. The
default block-cache size is `8MB`.
[...]
| kv.rocksdb.block.cache-index-and-filter-blocks | Boolean | false
| If true, index and filter blocks will be stored in block
cache, together with all other data blocks. This helps to limit memory usage so
that the total memory used by RocksDB is bounded by block cache size. The
default value is `false`.
[...]
-| kv.rocksdb.block.cache-index-and-filter-blocks-with-high-priority | Boolean
| false | If true and cache_index_and_filter_blocks is
enabled, index and filter blocks will be stored with high priority in block
cache, making them less likely to be evicted than data blocks. The default
value is `false`.
[...]
+| kv.rocksdb.block.cache-index-and-filter-blocks-with-high-priority | Boolean
| false | If true and cache_index_and_filter_blocks is
enabled, index and filter blocks will be stored with high priority in block
cache, making them less likely to be evicted than data blocks. The default
value is `false`.
[...]
| kv.rocksdb.block.pin-l0-filter-and-index-blocks-in-cache | Boolean | false
| If true and cache_index_and_filter_blocks is enabled,
L0 index and filter blocks will be pinned in block cache and will not be
evicted. This helps avoid performance degradation due to cache misses on L0
index/filter blocks. The default value is `false`.
[...]
| kv.rocksdb.block.pin-top-level-index-and-filter | Boolean | false
| If true, the top-level index of partitioned index/filter
blocks will be pinned in block cache and will not be evicted. The default value
is `false`.
[...]
| kv.rocksdb.use-bloom-filter | Boolean | true
| If true, every newly created SST file will contain a Bloom
filter. It is enabled by default.
[...]
diff --git a/website/docs/maintenance/tiered-storage/remote-storage.md
b/website/docs/maintenance/tiered-storage/remote-storage.md
index 34463bd68..0376e0a40 100644
--- a/website/docs/maintenance/tiered-storage/remote-storage.md
+++ b/website/docs/maintenance/tiered-storage/remote-storage.md
@@ -57,4 +57,4 @@ Below is the list for all configurations to control the
snapshot behavior in clu
| kv.snapshot.interval | Duration | 10min | The interval to
perform periodic snapshot for kv data.
|
| kv.snapshot.scheduler-thread-num | Integer | 1 | The number of
threads that the server uses to schedule snapshot kv data for all the replicas
in the server.
|
| kv.snapshot.transfer-thread-num | Integer | 4 | The number of
threads the server uses to transfer (download and upload) kv snapshot files.
|
-| kv.snapshot.num-retained | Integer | 1 | The maximum number
of completed snapshots to retain. It's recommended to set it to a larger value
to avoid the case that server delete the snapshot while the client is still
reading the snapshot. |
+| kv.snapshot.num-retained | Integer | 2 | The maximum number
of completed snapshots to retain. It's recommended to set it to a larger value
to avoid the case that server delete the snapshot while the client is still
reading the snapshot. |
