platinumhamburg opened a new issue, #2393: URL: https://github.com/apache/fluss/issues/2393
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Motivation Currently, Fluss does not expose RocksDB's block cache configuration options for index and filter blocks. By default, RocksDB stores index and filter blocks outside of the block cache, which means: 1. Users cannot control the memory usage of index and filter blocks 2. Memory usage can grow unbounded as more SST files are created 3. The total memory used by RocksDB is not bounded by the configured block cache size By exposing these configuration options, users can: - Store index and filter blocks in the block cache to limit total memory usage - Configure priority settings to prevent important blocks from being evicted - Pin critical blocks (L0 and top-level) to avoid performance degradation ### Solution Add configuration options to allow users to control how RocksDB handles index and filter blocks in the block cache. This enables better memory management and helps prevent unbounded memory growth in RocksDB instances. ### Anything else? _No response_ ### Willingness to contribute - [x] I'm willing to submit a PR! -- 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]
