docs/en/administration/management/BE_parameters/shared_lake_other.md
import BEConfigMethod from '../../../_assets/commonMarkdown/BE_config_method.mdx'
import CNConfigMethod from '../../../_assets/commonMarkdown/CN_config_method.mdx'
import PostBEConfig from '../../../_assets/commonMarkdown/BE_dynamic_note.mdx'
import StaticBEConfigNote from '../../../_assets/commonMarkdown/StaticBE_config_note.mdx'
You can view the BE configuration items using the following command:
SELECT * FROM information_schema.be_configs [WHERE NAME LIKE "%<name_pattern>%"]
This topic introduces the following types of FE configurations:
0 to disable this early-flush strategy.0 to disable this early-flush strategy. Works in conjunction with cloud_native_pk_index_rebuild_files_threshold; a flush is triggered if either threshold is exceeded.5 to 1000 since v3.2.4 and v3.1.10, and to 500 since v3.3.1 and v3.2.9. After the Sized-tiered Compaction policy is enabled for Primary Key tables (by setting enable_pk_size_tiered_compaction_strategy to true), StarRocks does not need to limit the number of rowsets for each compaction to reduce write amplification. Therefore, the default value of this parameter is increased.0 to disable the loop wait. From v3.4 onwards, this item is changed to mutable and its default value is changed from 0 to 2.datacache_unified_instance_enable is false.true indicates enabling this feature and false indicates disabling it. The default value is set from false to true from v3.2.3 onwards.datacache_disk_low_level for longer than this duration.80%) or a physical limit (for example, 2T, 500G). For example, if you use two disks and set the value of the datacache_disk_size parameter as 21474836480 (20 GB), a maximum of 40 GB data can be cached on these two disks. The default value is 0, which indicates that only memory is used to cache data.true indicates Data Cache is enabled, and false indicates Data Cache is disabled. The default value is changed to true from v3.3.lru (least recently used) and slru (Segmented LRU).inline mode, which caches the block data and metadata together in memory.10%) or a physical limit (for example, 10G, 21474836480).0 to prevent suboptimal performance caused by frequent cache fills and evictions due to insufficient cache capacity.80 to 90. This item is renamed from datacache_disk_high_level to disk_high_level from v4.0 onwards.datacache_disk_idle_seconds_for_expansion, and the space allocated for Data Cache is fully utilized, the system will automatically expand the cache capacity by increasing the upper limit. This item is renamed from datacache_disk_low_level to disk_low_level from v4.0 onwards.70 to 80. This item is renamed from datacache_disk_safe_level to disk_safe_level from v4.0 onwards.datacache_auto_adjust_enable to enable_datacache_disk_auto_adjust from v4.0 onwards.jdbc_minimum_idle_connections.jdbc_url share the same connection pool.jdbc_connection_max_lifetime_ms. Invalid enabled values are silently disabled (reset to 0)..sst, .delvec, .del, .cols) during lake-to-lake (shared-data) cross-cluster replication. Each attempt verifies the copied file size matches the source to detect truncated copies caused by transient object storage issues. Increase this value if experiencing intermittent file corruption during replication over unreliable storage.0, no limit is imposed on the concurrency.default_mv_wg. The default value 0 indicates no limits.default_mv_wg.default_mv_wg. The default value indicates 80% of the memory.default_mv_wg triggers intermediate result spilling. The default value indicates 80% of the memory.error_urls debugging, whether to allow operators to choose between using original hostnames from FE heartbeat or forcing resolution to IP addresses based on their environment needs.
true: Resolve hostnames to IPs.false (Default): Keeps the original hostname in the error URL.retry_apply_interval_second multiplied by the current failure count and clamped to a 600s maximum, so backoff grows with successive failures. Explicitly non-retryable errors (for example corruption) bypass retries and cause the apply process to enter the error state immediately. Retries continue until an overall timeout/terminal condition is reached, after which the apply will enter the error state. Turning this off disables automatic rescheduling of failed apply tasks and causes failed applies to transition to error state without retries.true indicates enabling the token check, and false indicates disabling it.?scroll=<value>) and when sending subsequent scroll requests (via ESScrollQueryBuilder). This controls how long the ES search context is retained before garbage collection on the ES side; setting it longer keeps scroll contexts alive for more time but prolongs resource usage on the ES cluster. The value is read at startup by the ES scan reader and is not changeable at runtime.> memory_high, performs controlled eviction guided by the GC advisor; if consumption exceeds memory_urgent_level (a separate config), more aggressive immediate reductions occur. This value is also consulted to disable certain memory‑intensive operations (for example, primary-key preload) when the threshold is exceeded. Must satisfy validation with memory_urgent_level (memory_urgent_level > memory_high_level, memory_high_level >= 1, memory_urgent_level <= 100).${STARROCKS_HOME}/lib/small_file/${STARROCKS_HOME}/lib/udf