platinumhamburg commented on code in PR #3463: URL: https://github.com/apache/fluss/pull/3463#discussion_r3564250775
##########
website/docs/maintenance/configuration.md:
##########
@@ -174,6 +174,9 @@ during the Fluss cluster working.
| kv.rocksdb.bloom-filter.bits-per-key | Double | 10.0
| Bits per key that bloom filter will use, this only take
effect when bloom filter is used. The default value is 10.0.
|
| kv.rocksdb.bloom-filter.block-based-mode | Boolean | false
| If true, RocksDB will use block-based filter instead of
full filter, this only take effect when bloom filter is used. The default value
is `false`.
|
| kv.rocksdb.shared-rate-limiter-bytes-per-sec | MemorySize |
Long.MAX_VALUE | The bytes per second rate limit for RocksDB
flush and compaction operations shared across all RocksDB instances on the
TabletServer. The rate limiter is always enabled. The default value is
Long.MAX_VALUE (effectively unlimited). Set to a lower value (e.g., 100MB) to
limit the rate. This configuration can be updated dynamically without server
restart. See [Updating Configs](operations/updating-configs.md) for more
details.
|
+| kv.backpressure.l0-slowdown-trigger | Integer | 8
| The L0 file count at which Fluss starts emitting proactive
backpressure signals to clients. This value should be lower than the underlying
storage engine's own L0 slowdown trigger (RocksDB
`level0_slowdown_writes_trigger`, default `20`), so that clients begin
throttling before the storage engine is forced to throttle itself. The gap
between this value and the storage trigger forms the throttle ramp-up window.
The default value is `8`.
|
+| kv.flush.thread-num | Integer | 10
| The number of threads that the server uses to asynchronously
flush primary-key table writes to RocksDB. The default value is 10. |
+| client.writer.kv-backpressure.max-throttle | Duration | 3s
| The upper bound of the per-bucket throttle delay the client
applies in response to KV backpressure signals piggybacked by the server.
Throttle delay is computed as: `max_throttle * p^2`, where `p` is the
normalized pressure in `[0, 1)` reported by the server. Once the server rejects
a write with `StorageBackpressureException`, the client also uses this value as
the initial retry backoff so that the transition between throttle and rejection
is continuous. The default value is 3 seconds. |
Review Comment:
PR description updated.
--
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]
