Версия: 2.0.x

Конфигурация FE

Параметры FE делятся на динамические и статические.

Динамические параметры можно настраивать и изменять с помощью SQL-команд, что очень удобно. Однако эти настройки становятся недействительными при перезапуске FE. Поэтому мы рекомендуем также изменять параметры конфигурации в файле fe.conf, чтобы предотвратить потерю изменений.
Статические параметры можно настраивать и изменять только в конфигурационном файле FE fe.conf. После изменения этого файла необходимо перезапустить FE, чтобы изменения вступили в силу.

Является ли параметр динамическим, указано в столбце IsMutable в выводе ADMIN SHOW CONFIG. TRUE означает динамический параметр.

Обратите внимание, что как динамические, так и статические параметры FE можно настраивать в файле fe.conf.

Просмотр параметров конфигурации FE

После запуска FE вы можете выполнить команду ADMIN SHOW FRONTEND CONFIG в вашем MySQL-клиенте для проверки конфигурации параметров. Если вы хотите запросить конфигурацию конкретного параметра, выполните следующую команду:

ADMIN SHOW FRONTEND CONFIG [LIKE "pattern"];

Для подробного описания возвращаемых полей см. ADMIN SHOW CONFIG.

примечание

У вас должны быть права администратора для выполнения команд, связанных с администрированием cluster.

Настройка параметров FE

Настройка динамических параметров FE

Вы можете настроить или изменить настройки динамических параметров FE с помощью ADMIN SET FRONTEND CONFIG.

ADMIN SET FRONTEND CONFIG ("key" = "value");

примечание

Изменения конфигурации, сделанные с помощью ADMIN SET FRONTEND, будут сброшены к значениям по умолчанию из файла fe.conf после перезапуска FE. Поэтому мы рекомендуем также изменить параметры конфигурации в fe.conf, если вы хотите сделать изменения постоянными.

Настройка статических параметров FE

примечание

Статические параметры FE задаются путём их изменения в конфигурационном файле fe.conf и перезапуска FE для вступления изменений в силу.

Описание параметров FE

Logging

log_roll_size_mb

Default: 1024
Type: Int
Unit: MB
Is mutable: No
Description: Максимум size of a system файл лога or an audit файл лога.
Introduced in: -

sys_log_dir

Default: SelenaFE.SELENA_HOME_DIR + "/log"
Type: String
Unit: -
Is mutable: No
Description: Директория которая хранит system файл логаs.
Introduced in: -

sys_log_level

Default: INFO
Type: String
Unit: -
Is mutable: No
Description: The severity levels into which system записей лога are classified. Допустимые значения: INFO, WARN, ERROR, and FATAL.
Introduced in: -

sys_log_roll_num

Default: 10
Type: Int
Unit: -
Is mutable: No
Description: Максимальное количество system файл логаs that может сохраняться within каждый период хранения указанного параметром the sys_log_roll_interval parameter.
Introduced in: -

sys_log_verbose_modules

Default: Empty string
Type: String[]
Unit: -
Is mutable: No
Description: The modules for which Selena генерирует системный логs. Если этот параметр установлен в org.apache.selena.catalog, Selena генерирует системный логs only for the catalog module. Разделите the имена модулей запятой (,) и пробелом.
Introduced in: -

sys_log_roll_interval

Default: DAY
Type: String
Unit: -
Is mutable: No
Description: Интервал времени с которым Selena ротирует system записей лога. Допустимые значения: DAY and HOUR.
- Если этот параметр установлен в DAY, суффикс в формате yyyyMMdd добавляется к именам of system файл логаs.
- Если этот параметр установлен в HOUR, суффикс в формате yyyyMMddHH добавляется к именам of system файл логаs.
Introduced in: -

sys_log_delete_age

Default: 7d
Type: String
Unit: -
Is mutable: No
Description: The период хранения of system файл логаs. The default value 7d указывает, что каждый system файл лога может сохраняться for 7 days. Selena проверяет каждый system файл лога and удаляет те которые были сгенерированы 7 дней назад.
Introduced in: -

audit_log_dir

Default: SelenaFE.SELENA_HOME_DIR + "/log"
Type: String
Unit: -
Is mutable: No
Description: Директория которая хранит audit файл логаs.
Introduced in: -

audit_log_roll_num

Default: 90
Type: Int
Unit: -
Is mutable: No
Description: Максимальное количество audit файл логаs that может сохраняться within каждый период хранения указанного параметром the audit_log_roll_interval parameter.
Introduced in: -

audit_log_modules

Default: slow_query, query
Type: String[]
Unit: -
Is mutable: No
Description: The modules for which Selena генерирует audit записей лога. По умолчанию, Selena генерирует лог аудитаs for the slow_query module and the query module. The connection module поддерживается начиная с версии v1.5.2. Разделите the имена модулей запятой (,) и пробелом.
Introduced in: -

qe_slow_log_ms

Default: 5000
Type: Long
Unit: Milliseconds
Is mutable: Yes
Description: Порог используется для determine whether a query is a медленный запрос. If the время ответа of a query exceeds этот порог, it записывается как a медленный запрос in fe.audit.log.
Introduced in: -

audit_log_roll_interval

Default: DAY
Type: String
Unit: -
Is mutable: No
Description: Интервал времени с которым Selena ротирует audit записей лога. Допустимые значения: DAY and HOUR.
- Если этот параметр установлен в DAY, суффикс в формате yyyyMMdd добавляется к именам of audit файл логаs.
- Если этот параметр установлен в HOUR, суффикс в формате yyyyMMddHH добавляется к именам of audit файл логаs.
Introduced in: -

audit_log_delete_age

Default: 30d
Type: String
Unit: -
Is mutable: No
Description: The период хранения of audit файл логаs. The default value 30d указывает, что каждый audit файл лога может сохраняться for 30 days. Selena проверяет каждый audit файл лога and удаляет те которые были сгенерированы 30 дней назад.
Introduced in: -

dump_log_dir

Default: SelenaFE.SELENA_HOME_DIR + "/log"
Type: String
Unit: -
Is mutable: No
Description: Директория которая хранит dump файл логаs.
Introduced in: -

dump_log_roll_num

Default: 10
Type: Int
Unit: -
Is mutable: No
Description: Максимальное количество dump файл логаs that может сохраняться within каждый период хранения указанного параметром the dump_log_roll_interval parameter.
Introduced in: -

dump_log_modules

Default: query
Type: String[]
Unit: -
Is mutable: No
Description: The modules for which Selena генерирует dump записей лога. По умолчанию, Selena генерирует лог дампаs for the query module. Разделите the имена модулей запятой (,) и пробелом.
Introduced in: -

dump_log_roll_interval

Default: DAY
Type: String
Unit: -
Is mutable: No
Description: Интервал времени с которым Selena ротирует dump записей лога. Допустимые значения: DAY and HOUR.
- Если этот параметр установлен в DAY, суффикс в формате yyyyMMdd добавляется к именам of dump файл логаs.
- Если этот параметр установлен в HOUR, суффикс в формате yyyyMMddHH добавляется к именам of dump файл логаs.
Introduced in: -

dump_log_delete_age

Default: 7d
Type: String
Unit: -
Is mutable: No
Description: The период хранения of dump файл логаs. The default value 7d указывает, что каждый dump файл лога может сохраняться for 7 days. Selena проверяет каждый dump файл лога and удаляет те которые были сгенерированы 7 дней назад.
Introduced in: -

log_cleaner_disk_util_based_enable

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Enable automatic log cleaning based on disk usage. When enabled, logs будет cleaned when disk usage exceeds the threshold. The log cleaner runs as a background daemon on the узел FE and helps prevent disk space exhaustion from файл лога accumulation.
Introduced in: -

log_cleaner_disk_usage_threshold

Default: 80
Type: Int
Unit: Percentage
Is mutable: Yes
Description: Disk usage threshold (наcentage) to trigger log cleaning. When disk usage exceeds этот порог, log cleaning will start. The cleaner проверяет каждый configured log directory independently and обрабатывает directories that exceed этот порог.
Introduced in: -

log_cleaner_disk_usage_target

Default: 60
Type: Int
Unit: Percentage
Is mutable: Yes
Description: Target disk usage (наcentage) after log cleaning. Log cleaning will continue until disk usage drops below этот порог. The cleaner deletes the oldest файл логаs one by one until the target is rкаждыйed.
Introduced in: -

log_cleaner_audit_log_min_retention_days

Default: 3
Type: Int
Unit: Days
Is mutable: Yes
Description: Minimum retention days for audit файл логаs. Audit файл логаs newer than this will not be deleted even if disk usage is high. This гарантирует, что лог аудитаs are preserved for compliance and troubleshooting purposes.
Introduced in: -

log_cleaner_check_interval_second

Default: 300
Type: Int
Unit: Seconds
Is mutable: Yes
Description: Interval в секундах для проверки disk usage and clean logs. The cleaner наiodicвсеy проверяет каждый log directory's disk usage and triggers cleaning when necessary. Default is 300 seconds (5 minutes).
Introduced in: -

Server

frontend_address

Default: 0.0.0.0
Type: String
Unit: -
Is mutable: No
Description: The IP address of the узел FE.
Introduced in: -

dns_cache_ttl_seconds

Default: 60
Type: Int
Unit: Seconds
Is mutable: No
Description: DNS cache TTL (Time-To-Live) в секундах for successful DNS lookups. This sets the Java security proнаty networkaddress.cache.ttl which controls how long the JVM caches successful DNS lookups. Set to -1 to cache forever, or 0 чтобы отключить caching. This is particularly useful in environments where IP addresses change frequently, such as Kubernetes deployments or when using dynamic DNS. This is a static configuration and requires FE restart to take effect.
Introduced in: v1.5.2, v2.0.0

priority_networks

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: Declares a selection strategy for servers that иметь multiple IP addresses. Note that at most one IP address must match the list указанного параметром this parameter. The value of this parameter is a list that consists of entries, which are separated with semicolons (;) in CIDR notation, such as 10.10.10.0/24. If no IP address matches the entries in this list, an available IP address of the server будет randomly selected. From v1.5.2, Selena supports deployment based on IPv6. If the server имеет both IPv4 and IPv6 addresses, and this parameter is not specified, the system uses an IPv4 address по умолчанию. You can change this behavior by настройка net_use_ipv6_when_priority_networks_empty to true.
Introduced in: -

net_use_ipv6_when_priority_networks_empty

Default: false
Type: Boolean
Unit: -
Is mutable: No
Description: A boolean value чтобы управлять whether to use IPv6 addresses preferentiвсеy when priority_networks is not specified. true означает to всеow the system to use an IPv6 address preferentiвсеy when the server that hosts the node имеет both IPv4 and IPv6 addresses and priority_networks is not specified.
Introduced in: v1.5.2

http_port

Default: 8030
Type: Int
Unit: -
Is mutable: No
Description: The port on which the HTTP server in the узел FE listens.
Introduced in: -

http_worker_threads_num

Default: 0
Type: Int
Unit: -
Is mutable: No
Description: Number of worker threads for http server to deal with http requests. For a negative or 0 value, the number of threads будет twice the number of cpu cores.
Introduced in: v1.5.2

http_backlog_num

Default: 1024
Type: Int
Unit: -
Is mutable: No
Description: The length of the backlog queue held by the HTTP server in the узел FE.
Introduced in: -

enable_http_async_handler

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, всеow the system to process HTTP-запросs asynchronously. If this feature включён, an HTTP-запрос received by Netty worker threads will then be submitted to a separate thread pool for service logic handling to avoid blocking the HTTP server. If disabled, Netty workers will handle the service logic.
Introduced in: 4.0.0

enable_https

Default: false
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, enable HTTPS server alongside HTTP server in узел FEs.
Introduced in: v2.0.0

https_port

Default: 8443
Type: Int
Unit: -
Is mutable: No
Description: The port on which the HTTPS server in the узел FE listens.
Introduced in: v2.0.0

http_async_threads_num

Default: 4096
Type: Int
Unit: -
Is mutable: Yes
Description: Size of the thread pool for asynchronous HTTP-запрос processing. The alias is max_http_sql_service_task_threads_num.
Introduced in: 4.0.0

cluster_name

Default: Selena Cluster
Type: String
Unit: -
Is mutable: No
Description: The name of the Selena cluster to which the FE belongs. The cluster name is displayed for Title on the web page.
Introduced in: -

rpc_port

Default: 9020
Type: Int
Unit: -
Is mutable: No
Description: The port on which the Thrift server in the узел FE listens.
Introduced in: -

thrift_server_max_worker_threads

Default: 4096
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество worker threads that поддерживаются by the Thrift server in the узел FE.
Introduced in: -

thrift_server_queue_size

Default: 4096
Type: Int
Unit: -
Is mutable: No
Description: The length of queue where requests are ожидающий. If the number of threads that are being processed in the thrift server exceeds the value specified in thrift_server_max_worker_threads, new requests are added to the ожидающий queue.
Introduced in: -

thrift_client_timeout_ms

Default: 5000
Type: Int
Unit: Milliseconds
Is mutable: No
Description: The length of time after which idle client connections time out.
Introduced in: -

thrift_backlog_num

Default: 1024
Type: Int
Unit: -
Is mutable: No
Description: The length of the backlog queue held by the Thrift server in the узел FE.
Introduced in: -

brpc_idle_wait_max_time

Default: 10000
Type: Int
Unit: ms
Is mutable: No
Description: Максимум length of time for which bRPC clients wait as in the idle state.
Introduced in: -

query_port

Default: 9030
Type: Int
Unit: -
Is mutable: No
Description: The port on which the MySQL server in the узел FE listens.
Introduced in: -

mysql_nio_backlog_num

Default: 1024
Type: Int
Unit: -
Is mutable: No
Description: The length of the backlog queue held by the MySQL server in the узел FE.
Introduced in: -

mysql_service_nio_enable_keep_alive

Default: true
Type: Boolean
Unit: -
Is mutable: No
Description: Enable TCP Keep-Alive for MySQL connections. Useful for long-idled connections behind load balancers.
Introduced in: -

mysql_service_io_threads_num

Default: 4
Type: Int
Unit: -
Is mutable: No
Description: Максимальное количество threads that может быть run by the MySQL server in the узел FE to process I/O events.
Introduced in: -

max_mysql_service_task_threads_num

Default: 4096
Type: Int
Unit: -
Is mutable: No
Description: Максимальное количество threads that может быть run by the MySQL server in the узел FE to process tasks.
Introduced in: -

mysql_server_version

Default: 8.0.33
Type: String
Unit: -
Is mutable: Yes
Description: The MySQL server version returned to the client. Modifying this parameter will affect the version information in the following situations:
1. select version();
2. Handshake packet version
3. Value of the global variable version (show variables like 'version';)
Introduced in: -

qe_max_connection

Default: 4096
Type: Int
Unit: -
Is mutable: No
Description: Максимальное количество connections that может быть established by все users to the узел FE. From v1.5.2 onwards, the default value имеет been changed from 1024 to 4096.
Introduced in: -

Metadata and cluster management

cluster_id

Default: -1
Type: Int
Unit: -
Is mutable: No
Description: The ID of the Selena cluster to which the FE belongs. FEs or BEs that иметь the same cluster ID belong to the same Selena cluster. Допустимые значения: любой positive integer. The default value -1 указывает, что Selena will generate a random cluster ID for the Selena cluster at the time when the leader FE of the cluster is started for the first time.
Introduced in: -

meta_dir

Default: SelenaFE.SELENA_HOME_DIR + "/meta"
Type: String
Unit: -
Is mutable: No
Description: Директория которая хранит metadata.
Introduced in: -

edit_log_type

Default: BDB
Type: String
Unit: -
Is mutable: No
Description: The type of edit log that может быть generated. Set the value to BDB.
Introduced in: -

edit_log_port

Default: 9010
Type: Int
Unit: -
Is mutable: No
Description: The port that is используется для communication among the Leader, Follower, and Observer FEs in the cluster.
Introduced in: -

edit_log_roll_num

Default: 50000
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество metadata записей лога that может быть written before a файл лога is created for these записей лога. Этот параметр is используется для control the size of файл логаs. The new файл лога is written to the BDBJE database.
Introduced in: -

metadata_ignore_unknown_oнаation_type

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, ignore an unknown log ID. When an FE is rolled back, the FEs of the earlier version may be unable to recognize some log IDs. Если значение is TRUE, the FE ignores unknown log IDs. Если значение is FALSE, the FE exits.
Introduced in: -

meta_delay_toleration_second

Default: 300
Type: Int
Unit: Seconds
Is mutable: Yes
Description: Максимум duration by which the metadata on the follower and observer FEs can lag behind that on the leader FE. Unit: seconds. If this duration is exceeded, the non-leader FEs stops providing services.
Introduced in: -

master_sync_policy

Default: SYNC
Type: String
Unit: -
Is mutable: No
Description: The policy based on which the leader FE flushes logs to disk. Этот параметр is valid только когда the current FE is a leader FE. Valid values:
- SYNC: When a transaction is committed, a log entry is generated and flushed to disk simultaneously.
- NO_SYNC: The generation and flushing of a log entry do not occur at the same time when a transaction is committed.
- WRITE_NO_SYNC: When a transaction is committed, a log entry is generated simultaneously but is not flushed to disk.
If you иметь deployed only one follower FE, we recommend that you set this parameter to SYNC. If you иметь deployed three or more follower FEs, we recommend that you set this parameter and the replica_sync_policy both to WRITE_NO_SYNC.
Introduced in: -

replica_sync_policy

Default: SYNC
Type: String
Unit: -
Is mutable: No
Description: The policy based on which the follower FE flushes logs to disk. Этот параметр is valid только когда the current FE is a follower FE. Valid values:
- SYNC: When a transaction is committed, a log entry is generated and flushed to disk simultaneously.
- NO_SYNC: The generation and flushing of a log entry do not occur at the same time when a transaction is committed.
- WRITE_NO_SYNC: When a transaction is committed, a log entry is generated simultaneously but is not flushed to disk.
Introduced in: -

replica_ack_policy

Default: SIMPLE_MAJORITY
Type: String
Unit: -
Is mutable: No
Description: The policy based on which a log entry is considered valid. The default value SIMPLE_MAJORITY указывает, что a log entry is considered valid if a majority of follower FEs return ACK messages.
Introduced in: -

bdbje_heartbeat_timeout_second

Default: 30
Type: Int
Unit: Seconds
Is mutable: No
Description: The amount of time after which the heartbeats among the leader, follower, and observer FEs in the Selena cluster time out.
Introduced in: -

bdbje_replica_ack_timeout_second

Default: 10
Type: Int
Unit: Seconds
Is mutable: No
Description: Максимум amount of time for which the leader FE can wait for ACK messages from a specified number of follower FEs when metadata is written from the leader FE to the follower FEs. Unit: second. If a large amount of metadata is being written, the follower FEs require a long time before they can return ACK messages to the leader FE, causing ACK timeout. In this situation, metadata writes fail, and the FE process exits. We recommend that you increase the value of this parameter to prevent this situation.
Introduced in: -

bdbje_lock_timeout_second

Default: 1
Type: Int
Unit: Seconds
Is mutable: No
Description: The amount of time after which a lock in the BDB JE-based FE times out.
Introduced in: -

bdbje_reset_election_group

Default: false
Type: String
Unit: -
Is mutable: No
Description: Определяет, reset the BDBJE replication group. Если этот параметр установлен в TRUE, the FE will reset the BDBJE replication group (that is, remove the information of все electable узел FEs) and start as the leader FE. After the reset, this FE будет the only member in the cluster, and other FEs can rejoin this cluster by using ALTER SYSTEM ADD/DROP FOLLOWER/OBSERVER 'xxx'. Use this настройка только когда no leader FE может быть elected because the data of most follower FEs иметь been damaged. reset_election_group is используется для replace metadata_failure_recovery.
Introduced in: -

max_bdbje_clock_delta_ms

Default: 5000
Type: Long
Unit: Milliseconds
Is mutable: No
Description: Максимум clock offset that is всеowed between the leader FE and the follower or observer FEs in the Selena cluster.
Introduced in: -

txn_rollback_limit

Default: 100
Type: Int
Unit: -
Is mutable: No
Description: Максимальное количество transactions that может быть rolled back.
Introduced in: -

heartbeat_mgr_threads_num

Default: 8
Type: Int
Unit: -
Is mutable: No
Description: Количество threads that может быть run by the Heartbeat Manager to run heartbeat tasks.
Introduced in: -

heartbeat_mgr_blocking_queue_size

Default: 1024
Type: Int
Unit: -
Is mutable: No
Description: The size of the blocking queue которая хранит heartbeat tasks run by the Heartbeat Manager.
Introduced in: -

catalog_try_lock_timeout_ms

Default: 5000
Type: Long
Unit: Milliseconds
Is mutable: Yes
Description: The timeout duration to obtain the global lock.
Introduced in: -

ignore_materialized_view_error

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, FE ignores the metadata exception caused by materialized view errors. If FE fails to start due to the metadata exception caused by materialized view errors, you can set this parameter to true to всеow FE to ignore the exception.
Introduced in: v1.5.2

ignore_meta_check

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, non-Leader FEs ignore the metadata gap from the Leader FE. Если значение is TRUE, non-Leader FEs ignore the metadata gap from the Leader FE and continue providing data reading services. Этот параметр ensures continuous data reading services even when you stop the Leader FE for a long наiod of time. Если значение is FALSE, non-Leader FEs do not ignore the metadata gap from the Leader FE and stop providing data reading services.
Introduced in: -

drop_backend_after_decommission

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, delete a BE after the BE is decommissioned. TRUE означает that the BE is deleted immediately after it is decommissioned. FALSE означает that the BE is not deleted after it is decommissioned.
Introduced in: -

enable_collect_query_detail_info

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, collect the profile of a query. Если этот параметр установлен в TRUE, the system collects the profile of the query. Если этот параметр установлен в FALSE, the system does not collect the profile of the query.
Introduced in: -

profile_info_format

Default: default
Type: String
Unit: -
Is mutable: Yes
Description: The format of the Profile output by the system. Допустимые значения: default and json. When set to default, Profile is of the default format. When set to json, the system outputs Profile in JSON format.
Introduced in: v1.5.2

enable_background_refresh_connector_metadata

Default: true in v1.5.2 and later and false in v1.5.2
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the наiodic Hive metadata cache refresh. After it включён, Selena polls the metastore (Hive Metastore or AWS Glue) of your Hive cluster, and refreshes the cached metadata of the frequently accessed Hive catalogs to наceive data changes. true означает чтобы включить the Hive metadata cache refresh, and false означает чтобы отключить it.
Introduced in: v1.5.2

background_refresh_metadata_interval_millis

Default: 600000
Type: Int
Unit: Milliseconds
Is mutable: Yes
Description: The interval between two consecutive Hive metadata cache refreshes.
Introduced in: v1.5.2

background_refresh_metadata_time_secs_since_last_access_secs

Default: 3600 * 24
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The expiration time of a Hive metadata cache refresh task. For the Hive catalog that имеет been accessed, if it имеет not been accessed for more than the specified time, Selena stops refreshing its cached metadata. For the Hive catalog that имеет not been accessed, Selena will not refresh its cached metadata.
Introduced in: v1.5.2

enable_statistics_collect_profile

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, generate profiles for statistics queries. You can set this item to true to всеow Selena to generate query profiles for queries on system statistics.
Introduced in: v1.5.2

metadata_enable_recovery_mode

Default: false
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, enable the metadata recovery mode. When this mode включён, if part of the cluster metadata is lost, it может быть restored based on the information from BE. Currently, only the version information of partitions может быть restored.
Introduced in: v1.5.2

black_host_history_sec

Default: 2 * 60
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The time duration for retaining historical connection failures of узел BEs in the BE Blacklist. If a узел BE is added to the BE Blacklist automaticвсеy, Selena will assess its connectivity and judge whether it может быть removed from the BE Blacklist. Within black_host_history_sec, only if a blacklisted узел BE имеет fewer connection failures than the threshold set in black_host_connect_failures_within_time, it может быть removed from the BE Blacklist.
Introduced in: v1.5.2

black_host_connect_failures_within_time

Default: 5
Type: Int
Unit: -
Is mutable: Yes
Description: Порог of connection failures всеowed for a blacklisted узел BE. If a узел BE is added to the BE Blacklist automaticвсеy, Selena will assess its connectivity and judge whether it может быть removed from the BE Blacklist. Within black_host_history_sec, only if a blacklisted узел BE имеет fewer connection failures than the threshold set in black_host_connect_failures_within_time, it может быть removed from the BE Blacklist.
Introduced in: v1.5.2

lock_manager_enabled

Default: true
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, enable the lock manager. The lock manager выполняет central management for locks. For example, it can control whether to refine the granularity of metadata locks from the database level to the table level.
Introduced in: v1.5.2

lock_manager_enable_using_fine_granularity_lock

Default: true
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, refine the granularity of metadata locks from the database level to the table level. After metadata locks are refined to the table level, lock conflicts and contentions может быть reduced, which improves load and query concurrency. Этот параметр only вступает в силу when lock_manager_enabled включён.
Introduced in: v1.5.2

enable_legacy_compatibility_for_replication

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the Legacy Compatibility for Replication. Selena may beиметь differently between the old and new versions, causing problems during cross-cluster data migration. Therefore, you must enable Legacy Compatibility for the target cluster before data migration and disable it after data migration is завершён. true означает enabling this mode.
Introduced in: v1.5.2

automated_cluster_snapshot_interval_seconds

Default: 600
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The interval с которым the Automated Cluster Snapshot tasks срабатывают.
Introduced in: v1.5.2

enable_table_name_case_insensitive

Default: false
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, enable case-insensitive processing on catalog names, database names, table names, view names, and materialized view names. Currently, table names are case-sensitive по умолчанию.
- After enabling this feature, все related names будет stored in lowercase, and все SQL commands containing these names will automaticвсеy convert them to lowercase.
- You can enable this feature только когда creating a cluster. After the cluster is started, the value of this configuration cannot be modified by любой means. Any attempt для изменения it will result in an error. FE will fail to start when it detects that the value of this параметр конфигурации is inconsistent with that when the cluster was first started.
- Currently, this feature does not support JDBC catalog and table names. Do not enable this feature if you want to наform case-insensitive processing on JDBC or ODBC data sources.
Introduced in: v2.0.0

txn_latency_metric_report_groups

Default: An empty string
Type: String
Unit: -
Is mutable: Yes
Description: A comma-separated list of transaction latency metric groups to report. Load types are categorized into logical groups for monitoring. When a group включён, its name is added as a 'type' label to transaction metrics. Допустимые значения: stream_load, routine_load, broker_load, insert, and compaction (availabl only for shared-data clusters). Example: "stream_load,routine_load".
Introduced in: v2.0.0

User, role, and privilege

privilege_max_total_roles_на_user

Default: 64
Type: Int
Unit:
Is mutable: Yes
Description: Максимальное количество roles a user can have.
Introduced in: v1.5.2

privilege_max_role_depth

Default: 16
Type: Int
Unit:
Is mutable: Yes
Description: Максимум role depth (level of inheritance) of a role.
Introduced in: v1.5.2

Query engine

publish_version_interval_ms

Default: 10
Type: Int
Unit: Milliseconds
Is mutable: No
Description: Интервал времени с которым release validation tasks are issued.
Introduced in: -

statistic_cache_columns

Default: 100000
Type: Long
Unit: -
Is mutable: No
Description: Количество rows that может быть cached for the statistics table.
Introduced in: -

statistic_cache_thread_pool_size

Default: 10
Type: Int
Unit: -
Is mutable: No
Description: The size of the thread-pool which будет используется для refresh statistic caches.
Introduced in: -

max_всеowed_in_element_num_of_delete

Default: 10000
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество elements всеowed for the IN predicate in a DELETE statement.
Introduced in: -

enable_materialized_view

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the creation of materialized views.
Introduced in: -

enable_materialized_view_spill

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable Intermediate Result Spilling for materialized view refresh tasks.
Introduced in: v1.5.2

enable_backup_materialized_view

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the BACKUP and RESTORE of asynchronous materialized views when backing up or restoring a specific database. If this item установлен в false, Selena will skip backing up asynchronous materialized views.
Introduced in: v1.5.2

enable_exнаimental_mv

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the asynchronous materialized view feature. TRUE означает this feature включён. From v1.5.2 onwards, this feature включён по умолчанию. For versions earlier than v1.5.2, this feature отключён по умолчанию.
Introduced in: v1.5.2

enable_colocate_mv_index

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, support colocating the synchronous materialized view index with the base table when creating a synchronous materialized view. If this item установлен в true, tablet sink will speed up the write наformance of synchronous materialized views.
Introduced in: v1.5.2

default_mv_refresh_immediate

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, refresh an asynchronous materialized view immediately after creation. When this item установлен в true, newly created materialized view будет refreshed immediately.
Introduced in: v1.5.2

enable_materialized_view_metrics_collect

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, collect monitoring metrics for asynchronous materialized views по умолчанию.
Introduced in: v1.5.2

enable_materialized_view_text_based_rewrite

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable text-based query rewrite по умолчанию. If this item установлен в true, the system builds the abstract syntax tree while creating an asynchronous materialized view.
Introduced in: v1.5.2

enable_mv_automatic_active_check

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the system to automaticвсеy check and re-activate the asynchronous materialized views that are set inactive because their base tables (views) had undergone Schema Change or had been dropped and re-created. Please note that this feature will not re-activate the materialized views that are manuвсеy set inactive by users.
Introduced in: v1.5.2

enable_active_materialized_view_schema_strict_check

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, strictly check the length consistency of тип данныхs when activating an inactive materialized view. When this item установлен в false, the activation of the materialized view is not affected if the length of the тип данныхs имеет changed in the base table.
Introduced in: v1.5.2

mv_active_checker_interval_seconds

Default: 60
Type: Long
Unit: Seconds
Is mutable: Yes
Description: When the background active_checker thread включён, the system will наiodicвсеy detect and automaticвсеy reactivate materialized views that became Inactive due to schema changes or rebuilds of their base tables (or views). Этот параметр controls the scheduling interval of the checker thread, в секундах. Значение по умолчанию — system-defined.
Introduced in: v1.5.2

default_mv_partition_refresh_number

Default: 1
Type: Int
Unit: -
Is mutable: Yes
Description: When a materialized view refresh involves multiple partitions, this parameter controls how mлюбой partitions are refreshed in a single batch по умолчанию. Starting начиная с версии version 3.3.0, the system defaults to refreshing one partition at a time to avoid potential out-of-memory (OOM) issues. In earlier versions, все partitions were refreshed at once по умолчанию, which could lead to memory exhaustion and task failure. However, note that when a materialized view refresh involves a large number of partitions, refreshing only one partition at a time may lead to excessive scheduling overhead, longer overвсе refresh time, and a large number of refresh records. In such cases, it рекомендуется to adjust this parameter appropriately to improve refresh efficiency and reduce scheduling costs.
Introduced in: v1.5.2

enable_udf

Default: false
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, enable UDF.
Introduced in: -

enable_decimal_v3

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, support the DECIMAL V3 тип данных.
Introduced in: -

enable_sql_blacklist

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable blacklist check for SQL queries. When this feature включён, queries in the blacklist cannot be executed.
Introduced in: -

dynamic_partition_enable

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the dynamic partitioning feature. When this feature включён, Selena dynamicвсеy creates partitions for new data and automaticвсеy deletes expired partitions to ensure the freshness of data.
Introduced in: -

dynamic_partition_check_interval_seconds

Default: 600
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The interval с которым new data is checked. If new data is detected, Selena automaticвсеy creates partitions for the data.
Introduced in: -

max_query_retry_time

Default: 2
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество query retries on an FE.
Introduced in: -

max_create_table_timeout_second

Default: 600
Type: Int
Unit: Seconds
Is mutable: Yes
Description: Максимум timeout duration for creating a table.
Introduced in: -

create_table_max_serial_replicas

Default: 128
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество replicas to create seriвсеy. If actual replica count exceeds this value, replicas будет created concurrently. Try to reduce this value if table creation is taking a long time to complete.
Introduced in: -

http_slow_request_threshold_ms

Default: 5000
Type: Int
Unit: Milliseconds
Is mutable: Yes
Description: If the время ответа for an HTTP-запрос exceeds the value указанного параметром this parameter, a log is generated to track this request.
Introduced in: v1.5.2

max_partitions_in_one_batch

Default: 4096
Type: Long
Unit: -
Is mutable: Yes
Description: Максимальное количество partitions that может быть created when you bulk create partitions.
Introduced in: -

max_running_rollup_job_num_на_table

Default: 1
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество rollup jobs can run in parвсеel for a table.
Introduced in: -

expr_children_limit

Default: 10000
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество child expressions всеowed in an expression.
Introduced in: -

max_planner_scalar_rewrite_num

Default: 100000
Type: Long
Unit: -
Is mutable: Yes
Description: Максимальное количество times that the optimizer can rewrite a scalar oнаator.
Introduced in: -

max_scalar_oнаator_optimize_depth

Default：256
Type：Int
Unit：-
Is mutable: Yes
Description: Максимум depth that ScalarOнаator optimization может быть applied.
Introduced in: -

max_scalar_oнаator_flat_children

Default：10000
Type：Int
Unit：-
Is mutable: Yes
Description：Максимальное количество flat children for ScalarOнаator. You can set this limit to prevent the optimizer from using too much memory.
Introduced in: -

enable_statistic_collect

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, collect statistics for the CBO. This feature включён по умолчанию.
Introduced in: -

enable_statistic_collect_on_first_load

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Controls automatic statistics collection and maintenance triggered by data loading oнаations. This includes:
- Statistics collection when data is first loaded into a partition (partition version equals 2).
- Statistics collection when data is loaded into empty partitions of multi-partition tables.
- Statistics copying and updating for INSERT OVERWRITE oнаations.
Decision Policy for Statistics Collection Type:
- For INSERT OVERWRITE: deltaRatio = |targetRows - sourceRows| / (sourceRows + 1)
  - If deltaRatio < statistic_sample_collect_ratio_threshold_of_first_load (Default: 0.1), statistics collection will not be наformed. Only the existing statistics будет copied.
  - Else, if targetRows > statistic_sample_collect_rows (Default: 200000), SAMPLE statistics collection используется.
  - Else, FULL statistics collection используется.
- For First Load: deltaRatio = loadRows / (totalRows + 1)
  - If deltaRatio < statistic_sample_collect_ratio_threshold_of_first_load (Default: 0.1), statistics collection will not be наformed.
  - Else, if loadRows > statistic_sample_collect_rows (Default: 200000), SAMPLE statistics collection используется.
  - Else, FULL statistics collection используется.
Synchronization Behavior:
- For DML statements (INSERT INTO/INSERT OVERWRITE): Synchronous mode with table lock. The load oнаation waits for statistics collection to complete (up to semi_sync_collect_statistic_await_seconds).
- For Stream Load and Broker Load: Asynchronous mode without lock. Statistics collection runs in background without blocking the load oнаation.
примечание
Disabling this configuration will prevent все loading-triggered statistics oнаations, including statistics maintenance for INSERT OVERWRITE, which may result in tables lacking statistics. If new tables are frequently created and data is frequently loaded, enabling this feature will increase memory and CPU overhead.
Introduced in: v1.5.2

enable_statistic_collect_on_update

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Controls whether UPDATE statements can trigger automatic statistics collection. When enabled, UPDATE oнаations that modify table data may schedule statistics collection through the same ingestion-based statistics framework controlled by enable_statistic_collect_on_first_load. Disabling this configuration skips statistics collection for UPDATE statements while keeping load-triggered statistics collection behavior unchanged.
Introduced in: v1.5.2, v2.0.0

semi_sync_collect_statistic_await_seconds

Default: 30
Type: Int
Unit: Seconds
Is mutable: Yes
Description: Maximum wait time for semi-synchronous statistics collection during DML oнаations (INSERT INTO and INSERT OVERWRITE statements). Stream Load and Broker Load use asynchronous mode and are not affected by this configuration. If statistics collection time exceeds this value, the load oнаation continues without waiting for collection to complete. This configuration works in conjunction with enable_statistic_collect_on_first_load.
Introduced in: v1.5.2

statistic_auto_analyze_start_time

Default: 00:00:00
Type: String
Unit: -
Is mutable: Yes
Description: The start time of automatic collection. Value range: 00:00:00 - 23:59:59.
Introduced in: -

statistic_auto_analyze_end_time

Default: 23:59:59
Type: String
Unit: -
Is mutable: Yes
Description: The end time of automatic collection. Value range: 00:00:00 - 23:59:59.
Introduced in: -

statistic_analyze_status_keep_second

Default: 3 * 24 * 3600
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The duration to retain the history of collection tasks. Значение по умолчанию — 3 days.
Introduced in: -

statistic_collect_interval_sec

Default: 5 * 60
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The interval for checking data updates during automatic collection.
Introduced in: -

statistic_update_interval_sec

Default: 24 * 60 * 60
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The interval с которым the cache of statistical information is updated.
Introduced in: -

enable_collect_full_statistic

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable automatic full statistics collection. This feature включён по умолчанию.
Introduced in: -

statistic_auto_collect_ratio

Default: 0.8
Type: Double
Unit: -
Is mutable: Yes
Description: Порог for determining whether the statistics for automatic collection are healthy. If statistics health is below этот порог, automatic collection срабатывает.
Introduced in: -

statistic_auto_collect_smвсе_table_rows

Default: 10000000
Type: Long
Unit: -
Is mutable: Yes
Description: Threshold для определения whether a table in an external data source (Hive, Iceberg, Hudi) is a smвсе table during automatic collection. If the table имеет rows меньше this value, the table is considered a smвсе table.
Introduced in: v1.5.2

statistic_max_full_collect_data_size

Default: 100 * 1024 * 1024 * 1024
Type: Long
Unit: bytes
Is mutable: Yes
Description: The data size threshold for the automatic collection of statistics. If the total size exceeds this value, then sampled collection is наformed instead of full.
Introduced in: -

statistic_collect_max_row_count_на_query

Default: 5000000000
Type: Long
Unit: -
Is mutable: Yes
Description: Максимальное количество rows для запроса for a single analyze task. An analyze task будет split into multiple queries if this value is exceeded.
Introduced in: -

statistic_sample_collect_rows

Default: 200000
Type: Long
Unit: -
Is mutable: Yes
Description: The row count threshold for deciding between SAMPLE and FULL statistics collection during loading-triggered statistics oнаations. If the number of loaded or changed rows exceeds этот порог (default 200,000), SAMPLE statistics collection используется; otherwise, FULL statistics collection используется. This настройка works in conjunction with enable_statistic_collect_on_first_load and statistic_sample_collect_ratio_threshold_of_first_load.
Introduced in: -

enable_predicate_columns_collection

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable predicate columns collection. If disabled, predicate columns will not be recorded during query optimization.
Introduced in: -

histogram_buckets_size

Default: 64
Type: Long
Unit: -
Is mutable: Yes
Description: The default bucket number for a histogram.
Introduced in: -

histogram_mcv_size

Default: 100
Type: Long
Unit: -
Is mutable: Yes
Description: Количество most common values (MCV) for a histogram.
Introduced in: -

histogram_sample_ratio

Default: 0.1
Type: Double
Unit: -
Is mutable: Yes
Description: The sampling ratio for a histogram.
Introduced in: -

histogram_max_sample_row_count

Default: 10000000
Type: Long
Unit: -
Is mutable: Yes
Description: Максимальное количество rows to collect for a histogram.
Introduced in: -

connector_table_query_trigger_task_schedule_interval

Default: 30
Type: Int
Unit: Second
Is mutable: Yes
Description: The interval с которым the Scheduler thread schedules the query-trigger background tasks. Этот параметр is to replace connector_table_query_trigger_analyze_schedule_interval introduced in v1.5.2. Here, the background tasks refer ANALYZE tasks in v1.5.2，and the collection task of low-cardinality columns' dictionary in versions later than v1.5.2.
Introduced in: v1.5.2

connector_table_query_trigger_analyze_smвсе_table_rows

Default: 10000000
Type: Int
Unit: -
Is mutable: Yes
Description: Порог for determining whether a table is a smвсе table for query-trigger ANALYZE tasks.
Introduced in: v1.5.2

connector_table_query_trigger_analyze_smвсе_table_interval

Default: 2 * 3600
Type: Int
Unit: Second
Is mutable: Yes
Description: The interval for query-trigger ANALYZE tasks of smвсе tables.
Introduced in: v1.5.2

connector_table_query_trigger_analyze_large_table_interval

Default: 12 * 3600
Type: Int
Unit: Second
Is mutable: Yes
Description: The interval for query-trigger ANALYZE tasks of large tables.
Introduced in: v1.5.2

connector_table_query_trigger_analyze_max_ожидающий_task_num

Default: 100
Type: Int
Unit: -
Is mutable: Yes
Description: Maximum number of query-trigger ANALYZE tasks that are in Pending state on the FE.
Introduced in: v1.5.2

connector_table_query_trigger_analyze_max_running_task_num

Default: 2
Type: Int
Unit: -
Is mutable: Yes
Description: Maximum number of query-trigger ANALYZE tasks that are in Running state on the FE.
Introduced in: v1.5.2

enable_local_replica_selection

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, select local replicas for queries. Local replicas reduce the network transmission cost. Если этот параметр установлен в TRUE, the CBO preferentiвсеy selects tablet replicas on BEs that иметь the same IP address as the current FE. Если этот параметр установлен в FALSE, both local replicas and non-local replicas может быть selected.
Introduced in: -

max_distribution_pruner_recursion_depth

Default: 100
Type: Int
Unit: -
Is mutable: Yes
Description:: Максимум recursion depth всеowed by the partition pruner. Increasing the recursion depth can prune more elements but also increases CPU consumption.
Introduced in: -

slow_query_analyze_threshold

Default: 5
Type: Int
Unit: Seconds
Is mutable: Yes
Description:: The execution time threshold for queries to trigger the analysis of Query Feedback.
Introduced in: v1.5.2

low_cardinality_threshold

Default: 255
Type: Int
Unit: -
Is mutable: No
Description: Threshold of low cardinality dictionary.
Introduced in: v1.5.2

enable_manual_collect_array_ndv

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable manual collection for the NDV information of the ARRAY type.
Introduced in: v2.0.0

enable_auto_collect_array_ndv

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable automatic collection for the NDV information of the ARRAY type.
Introduced in: v2.0.0

Loading and unloading

load_straggler_wait_second

Default: 300
Type: Int
Unit: Seconds
Is mutable: Yes
Description: Максимум loading lag that может быть tolerated by a BE replica. Если это значение is exceeded, cloning is наformed to clone data from other replicas.
Introduced in: -

load_checker_interval_second

Default: 5
Type: Int
Unit: Seconds
Is mutable: No
Description: Интервал времени с которым load jobs are processed on a rolling basis.
Introduced in: -

broker_load_default_timeout_second

Default: 14400
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The timeout duration for a Broker Load job.
Introduced in: -

min_bytes_на_broker_scanner

Default: 67108864
Type: Long
Unit: Bytes
Is mutable: Yes
Description: Минимум всеowed amount of data that может быть processed by a Broker Load instance.
Introduced in: -

insert_load_default_timeout_second

Default: 3600
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The timeout duration for the INSERT INTO statement that is используется для load data.
Introduced in: -

stream_load_default_timeout_second

Default: 600
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The default timeout duration for каждый Stream Load job.
Introduced in: -

max_stream_load_timeout_second

Default: 259200
Type: Int
Unit: Seconds
Is mutable: Yes
Description: Максимум всеowed timeout duration for a Stream Load job.
Introduced in: -

max_load_timeout_second

Default: 259200
Type: Int
Unit: Seconds
Is mutable: Yes
Description: Максимум timeout duration всеowed for a load job. The load job fails if this limit is exceeded. This limit applies to все types of load jobs.
Introduced in: -

min_load_timeout_second

Default: 1
Type: Int
Unit: Seconds
Is mutable: Yes
Description: Минимум timeout duration всеowed for a load job. This limit applies to все types of load jobs.
Introduced in: -

prepared_transaction_default_timeout_second

Default: 86400
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The default timeout duration for a prepared transaction.
Introduced in: -

finish_transaction_default_lock_timeout_ms

Default: 1000
Type: Int
Unit: MilliSeconds
Is mutable: Yes
Description: The default timeout for acquiring the db and table lock during finishing transaction.
Introduced in: v2.0.0, v1.5.2

spark_dpp_version

Default: 1.0.0
Type: String
Unit: -
Is mutable: No
Description: The version of Spark Dynamic Partition Pruning (DPP) used.
Introduced in: -

spark_load_default_timeout_second

Default: 86400
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The timeout duration for каждый Spark Load job.
Introduced in: -

spark_home_default_dir

Default: SelenaFE.SELENA_HOME_DIR + "/lib/spark2x"
Type: String
Unit: -
Is mutable: No
Description: The root directory of a Spark client.
Introduced in: -

spark_resource_path

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The root directory of the Spark dependency package.
Introduced in: -

spark_launcher_log_dir

Default: sys_log_dir + "/spark_launcher_log"
Type: String
Unit: -
Is mutable: No
Description: Директория которая хранит Spark файл логаs.
Introduced in: -

yarn_client_path

Default: SelenaFE.SELENA_HOME_DIR + "/lib/yarn-client/hadoop/bin/yarn"
Type: String
Unit: -
Is mutable: No
Description: The root directory of the Yarn client package.
Introduced in: -

yarn_config_dir

Default: SelenaFE.SELENA_HOME_DIR + "/lib/yarn-config"
Type: String
Unit: -
Is mutable: No
Description: Директория которая хранит the Yarn configuration file.
Introduced in: -

desired_max_waiting_jobs

Default: 1024
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество ожидающий jobs in an FE. The number refers to все jobs, such as table creation, loading, and schema change jobs. If the number of ожидающий jobs in an FE rкаждыйes this value, the FE will reject new load requests. Этот параметр вступает в силу only for asynchronous loading. From v1.5.2 onwards, the default value is changed from 100 to 1024.
Introduced in: -

max_running_txn_num_на_db

Default: 1000
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество load transactions всеowed to be running for каждый database within a Selena cluster. Значение по умолчанию — 1000. From v1.5.2 onwards, the default value изменён на 1000 from 100. When the actual number of load transactions running for a database exceeds the value of this parameter, new load requests will not be processed. New requests for synchronous load jobs будет denied, and new requests for asynchronous load jobs будет placed in queue. We do not recommend you increase the value of this parameter because this will increase system load.
Introduced in: -

max_broker_load_job_concurrency

Default: 5
Alias: async_load_task_pool_size
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество concurrent Broker Load jobs всеowed within the Selena cluster. Этот параметр is valid only for Broker Load. The value of this parameter должен быть меньше the value of max_running_txn_num_на_db. From v1.5.2 onwards, the default value is changed from 10 to 5.
Introduced in: -

load_parвсеel_instance_num (Deprecated)

Default: 1
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество concurrent loading instances for каждый load job on a BE. Этот параметр is deprecated начиная с версии v1.5.2 onwards.
Introduced in: -

disable_load_job

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, disable loading when the cluster encounters an error. This prevents любой loss caused by cluster errors. Значение по умолчанию — FALSE, indicating that loading is not disabled. TRUE означает loading отключён and the cluster is in read-only state.
Introduced in: -

history_job_keep_max_second

Default: 7 * 24 * 3600
Type: Int
Unit: Seconds
Is mutable: Yes
Description: Максимум duration a historical job может сохраняться, such as schema change jobs.
Introduced in: -

label_keep_max_second

Default: 3 * 24 * 3600
Type: Int
Unit: Seconds
Is mutable: Yes
Description: Максимум duration в секундах to keep the labels of load jobs that иметь been завершён and are in the FINISHED or CANCELLED state. Значение по умолчанию — 3 days. After this duration expires, the labels будет deleted. Этот параметр applies to все types of load jobs. A value too large consumes a lot of memory.
Introduced in: -

label_keep_max_num

Default: 1000
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество load jobs that может сохраняться within a наiod of time. If this number is exceeded, the information of historical jobs будет deleted.
Introduced in: -

max_routine_load_task_concurrent_num

Default: 5
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество concurrent tasks for каждый Routine Load job.
Introduced in: -

max_routine_load_task_num_на_be

Default: 16
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество concurrent Routine Load tasks on каждый BE. Since v1.5.2, the default value for this parameter is increased to 16 from 5, and no longer needs to be меньше or равно the value of BE static parameter routine_load_thread_pool_size (deprecated).
Introduced in: -

max_routine_load_batch_size

Default: 4294967296
Type: Long
Unit: Bytes
Is mutable: Yes
Description: Максимум amount of data that может быть loaded by a Routine Load task.
Introduced in: -

routine_load_task_consume_second

Default: 15
Type: Long
Unit: Seconds
Is mutable: Yes
Description: Максимум time for каждый Routine Load task within the cluster to consume data. Since v1.5.2, Routine Load job supports a new parameter task_consume_second in job_proнаties. Этот параметр applies to individual load tasks within a Routine Load job, which is more flexible.
Introduced in: -

routine_load_task_timeout_second

Default: 60
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The timeout duration for каждый Routine Load task within the cluster. Since v1.5.2, Routine Load job supports a new parameter task_timeout_second in job_proнаties. Этот параметр applies to individual load tasks within a Routine Load job, which is more flexible.
Introduced in: -

routine_load_unstable_threshold_second

Default: 3600
Type: Long
Unit: Seconds
Is mutable: Yes
Description: Routine Load job установлен в the UNSTABLE state if любой task within the Routine Load job lags. To be specific, the difference between the timestamp of the message being consumed and the current time exceeds этот порог, and unconsumed messages exist in the data source.
Introduced in: -

enable_routine_load_lag_metrics

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, collect Routine Load Kafka partition offset lag metrics. Please note that set this item to true will cвсе the Kafka API to get the partition's latest offset.
Introduced in: -

min_routine_load_lag_for_metrics

Default: 10000
Type: INT
Unit: -
Is mutable: Yes
Description: Минимум offset lag of Routine Load jobs to be shown in monitoring metrics. Routine Load jobs whose offset lags are больше this value будет displayed in the metrics.
Introduced in: -

max_tolerable_backend_down_num

Default: 0
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество faulty узел BEs всеowed. If this number is exceeded, Routine Load jobs cannot be automaticвсеy recovered.
Introduced in: -

наiod_of_auto_resume_min

Default: 5
Type: Int
Unit: Minutes
Is mutable: Yes
Description: The interval с которым Routine Load jobs are automaticвсеy recovered.
Introduced in: -

export_task_default_timeout_second

Default: 2 * 3600
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The timeout duration for a data exporting task.
Introduced in: -

export_max_bytes_на_be_на_task

Default: 268435456
Type: Long
Unit: Bytes
Is mutable: Yes
Description: Максимум amount of data that может быть exported from a single BE by a single data unload task.
Introduced in: -

export_task_pool_size

Default: 5
Type: Int
Unit: -
Is mutable: No
Description: The size of the unload task thread pool.
Introduced in: -

export_checker_interval_second

Default: 5
Type: Int
Unit: Seconds
Is mutable: No
Description: Интервал времени с которым load jobs are scheduled.
Introduced in: -

export_running_job_num_limit

Default: 5
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество data exporting tasks that can run in parвсеel.
Introduced in: -

empty_load_as_error

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, return an error message "все partitions иметь no load data" if no data is loaded. Valid values:
- true: If no data is loaded, the system displays a failure message and returns an error "все partitions иметь no load data".
- false: If no data is loaded, the system displays a success message and returns OK, instead of an error.
Introduced in: -

external_table_commit_timeout_ms

Default: 10000
Type: Int
Unit: Milliseconds
Is mutable: Yes
Description: The timeout duration for committing (publishing) a write transaction to a Selena external table. The default value 10000 означает a 10-second timeout duration.
Introduced in: -

enable_sync_publish

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, synchronously execute the apply task at the publish phase of a load transaction. Этот параметр is applicable only to Primary Key tables. Valid values:
- TRUE (default): The apply task is synchronously executed at the publish phase of a load transaction. It означает, что the load transaction is reported as successful only after the apply task is завершён, and the loaded data can truly be queried. When a task loads a large volume of data at a time or loads data frequently, настройка this parameter to true can improve query наformance and stability, but may increase load latency.
- FALSE: The apply task is asynchronously executed at the publish phase of a load transaction. It означает, что the load transaction is reported as successful after the apply task is submitted, but the loaded data cannot be immediately queried. In this case, concurrent queries need to wait for the apply task to complete or time out before they can continue. When a task loads a large volume of data at a time or loads data frequently, настройка this parameter to false may affect query наformance and stability.
Introduced in: v1.5.2

label_clean_interval_second

Default: 4 * 3600
Type: Int
Unit: Seconds
Is mutable: No
Description: Интервал времени с которым labels are cleaned up. Unit: second. We recommend that you specify a short time interval to ensure that historical labels может быть cleaned up in a timely manner.
Introduced in: -

transaction_clean_interval_second

Default: 30
Type: Int
Unit: Seconds
Is mutable: No
Description: Интервал времени с которым finished transactions are cleaned up. Unit: second. We recommend that you specify a short time interval to ensure that finished transactions может быть cleaned up in a timely manner.
Introduced in: -

transaction_stream_load_coordinator_cache_capacity

Default: 4096
Type: Int
Unit: -
Is mutable: Yes
Description: The capacity of the cache которая хранит the mapping from transaction label to coordinator node.
Introduced in: -

transaction_stream_load_coordinator_cache_expire_seconds

Default: 900
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The time to keep the coordinator mapping in the cache before it's evicted(TTL).
Introduced in: -

enable_file_bundling

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the File Bundling optimization for the cloud-native table. When this feature включён (set to true), the system automaticвсеy bundles the файл данныхs generated by loading, Compaction, or Publish oнаations, thereby reducing the API cost caused by high-frequency access to the external storage system. You can also control this behavior on the table level using the CREATE TABLE proнаty file_bundling. For detailed instructions, see CREATE TABLE.
Introduced in: v2.0.0

Storage

default_replication_num

Default: 3
Type: Short
Unit: -
Is mutable: Yes
Description: Sets the default number of replicas for каждый data partition when creating a table in Selena. This настройка может быть overridden when creating a table by specifying replication_num=x in the CREATE TABLE DDL.
Introduced in: -

enable_strict_storage_medium_check

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, the FE strictly checks the storage medium of BEs when users create tables. Если этот параметр установлен в TRUE, the FE checks the storage medium of BEs when users create tables and returns an error if the storage medium of the BE is different from the storage_medium parameter specified in the CREATE TABLE statement. For example, the storage medium specified in the CREATE TABLE statement is SSD but the actual storage medium of BEs is HDD. As a result, the table creation fails. Если этот параметр is FALSE, the FE does not check the storage medium of BEs when users create a table.
Introduced in: -

catalog_trash_expire_second

Default: 86400
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The longest duration the metadata может сохраняться after a database, table, or partition is dropped. If this duration expires, the data будет deleted and cannot be recovered through the RECOVER command.
Introduced in: -

partition_recycle_retention_наiod_secs

Default: 1800
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The metadata retention time for the partition that is dropped by INSERT OVERWRITE or materialized view refresh oнаations. Note that such metadata cannot be recovered by executing RECOVER.
Introduced in: v1.5.2

enable_auto_tablet_distribution

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, automaticвсеy set the number of buckets.
- Если этот параметр установлен в TRUE, you don't need чтобы указать the number of buckets when you create a table or add a partition. Selena automaticвсеy determines the number of buckets.
- Если этот параметр установлен в FALSE, you need to manuвсеy specify the number of buckets when you create a table or add a partition. If you do not specify the bucket count when adding a new partition to a table, the new partition inherits the bucket count set at the creation of the table. However, you can also manuвсеy specify the number of buckets for the new partition.
Introduced in: v1.5.2

enable_exнаimental_rowstore

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the hybrid row-column storage feature.
Introduced in: v1.5.2

enable_exнаimental_gin

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the full-text inverted index feature.
Introduced in: v1.5.2

storage_usage_soft_limit_наcent

Default: 90
Alias: storage_high_watermark_usage_наcent
Type: Int
Unit: -
Is mutable: Yes
Description: Soft limit of the storage usage наcentage in a BE directory. If the storage usage (in наcentage) of the BE storage directory exceeds this value and the remaining storage space is меньше storage_usage_soft_limit_reserve_bytes, tablets cannot be cloned into this directory.
Introduced in: -

storage_usage_soft_limit_reserve_bytes

Default: 200 * 1024 * 1024 * 1024
Alias: storage_min_left_capacity_bytes
Type: Long
Unit: Bytes
Is mutable: Yes
Description: Soft limit of the remaining storage space in a BE directory. If the remaining storage space in the BE storage directory is меньше this value and the storage usage (in наcentage) exceeds storage_usage_soft_limit_наcent, tablets cannot be cloned into this directory.
Introduced in: -

storage_usage_hard_limit_наcent

Default: 95
Alias: storage_flood_stage_usage_наcent
Type: Int
Unit: -
Is mutable: Yes
Description: Hard limit of the storage usage наcentage in a BE directory. If the storage usage (in наcentage) of the BE storage directory exceeds this value and the remaining storage space is меньше storage_usage_hard_limit_reserve_bytes, Load and Restore jobs are rejected. You need to set this item together with the BE параметр конфигурации storage_flood_stage_usage_наcent to всеow the configurations to take effect.
Introduced in: -

storage_usage_hard_limit_reserve_bytes

Default: 100 * 1024 * 1024 * 1024
Alias: storage_flood_stage_left_capacity_bytes
Type: Long
Unit: Bytes
Is mutable: Yes
Description: Hard limit of the remaining storage space in a BE directory. If the remaining storage space in the BE storage directory is меньше this value and the storage usage (in наcentage) exceeds storage_usage_hard_limit_наcent, Load and Restore jobs are rejected. You need to set this item together with the BE параметр конфигурации storage_flood_stage_left_capacity_bytes to всеow the configurations to take effect.
Introduced in: -

alter_table_timeout_second

Default: 86400
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The timeout duration for the schema change oнаation (ALTER TABLE).
Introduced in: -

enable_fast_schema_evolution

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable fast schema evolution for все tables within the Selena cluster. Допустимые значения: TRUE and FALSE (default). Enabling fast schema evolution can increase the speed of schema changes and reduce resource usage when columns are added or dropped.
Introduced in: v1.5.2

NOTE

Selena shared-data clusters supports this parameter начиная с версии v1.5.2.

If you need для настройки the fast schema evolution for a specific table, such as disabling fast schema evolution for a specific table, you can set the table proнаty fast_schema_evolution at table creation.

recover_with_empty_tablet

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, replace a lost or corrupted tablet replica with an empty one. If a tablet replica is lost or corrupted, data queries on this tablet or other healthy tablets may fail. Replacing the lost or corrupted tablet replica with an empty tablet гарантирует, что the query can still be executed. However, the result may be incorrect because data is lost. Значение по умолчанию — FALSE, which means lost or corrupted tablet replicas are not replaced with empty ones, and the query fails.
Introduced in: -

tablet_checker_lock_time_на_cycle_ms

Default: 1000
Type: Int
Unit: Milliseconds
Is mutable: Yes
Description: Максимум lock hold time на cycle for tablet checker before releasing and reacquiring the table lock. Values меньше 100 будет treated as 100.
Introduced in: v1.5.2, v2.0.0

tablet_create_timeout_second

Default: 10
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The timeout duration for creating a tablet. Значение по умолчанию — changed from 1 to 10 начиная с версии v1.5.2 onwards.
Introduced in: -

tablet_delete_timeout_second

Default: 2
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The timeout duration for deleting a tablet.
Introduced in: -

check_consistency_default_timeout_second

Default: 600
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The timeout duration for a replica consistency check. You can set this parameter based on the size of your tablet.
Introduced in: -

tablet_sched_slot_num_на_path

Default: 8
Alias: schedule_slot_num_на_path
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество tablet-related tasks that can run concurrently in a BE storage directory. From v1.5.2 onwards, the default value of this parameter is changed from 4 to 8.
Introduced in: -

tablet_sched_max_scheduling_tablets

Default: 10000
Alias: max_scheduling_tablets
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество tablets that может быть scheduled at the same time. Если значение is exceeded, tablet balancing and repair checks будет skipped.
Introduced in: -

tablet_sched_disable_balance

Default: false
Alias: disable_balance
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, disable tablet balancing. TRUE означает that tablet balancing отключён. FALSE означает that tablet balancing включён.
Introduced in: -

tablet_sched_disable_colocate_balance

Default: false
Alias: disable_colocate_balance
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, disable replica balancing for Colocate Table. TRUE означает replica balancing отключён. FALSE означает replica balancing включён.
Introduced in: -

tablet_sched_be_down_tolerate_time_s

Default: 900
Type: Long
Unit: Seconds
Is mutable: Yes
Description: Максимум duration the scheduler всеows for a узел BE to remain inactive. After the time threshold is rкаждыйed, tablets on that узел BE будет migrated to other active узел BEs.
Introduced in: v1.5.2

tablet_sched_max_balancing_tablets

Default: 500
Alias: max_balancing_tablets
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество tablets that может быть balanced at the same time. Если это значение is exceeded, tablet re-balancing будет skipped.
Introduced in: -

tablet_sched_storage_cooldown_second

Default: -1
Alias: storage_cooldown_second
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The latency of automatic cooling starting from the time of table creation. The default value -1 указывает, что automatic cooling отключён. If you want чтобы включить automatic cooling, set this parameter to a value больше -1.
Introduced in: -

tablet_sched_max_not_being_scheduled_interval_ms

Default: 15 * 60 * 1000
Type: Long
Unit: Milliseconds
Is mutable: Yes
Description: When the tablet clone tasks are being scheduled, if a tablet имеет not been scheduled for the specified time in this parameter, Selena gives it a higher priority to schedule it as soon as possible.
Introduced in: -

tablet_sched_balance_load_score_threshold

Default: 0.1
Alias: balance_load_score_threshold
Type: Double
Unit: -
Is mutable: Yes
Description: The наcentage threshold for determining whether the load of a BE is balanced. If a BE имеет a lower load than the average load of все BEs and the difference is больше this value, this BE is in a low load state. On the contrary, if a BE имеет a higher load than the average load and the difference is больше this value, this BE is in a high load state.
Introduced in: -

tablet_sched_num_based_balance_threshold_ratio

Default: 0.5
Alias: -
Type: Double
Unit: -
Is mutable: Yes
Description: Doing num based balance may break the disk size balance, but the maximum gap between disks cannot exceed tablet_sched_num_based_balance_threshold_ratio * tablet_sched_balance_load_score_threshold. If there are tablets in the cluster that are constantly balancing from A to B and B to A, reduce this value. If you want the tablet distribution to be more balanced, increase this value.
Introduced in: - 3.1

tablet_sched_balance_load_disk_safe_threshold

Default: 0.5
Alias: balance_load_disk_safe_threshold
Type: Double
Unit: -
Is mutable: Yes
Description: The наcentage threshold for determining whether the disk usage of BEs is balanced. If the disk usage of все BEs is ниже this value, it is considered balanced. If the disk usage is больше this value and the difference between the highest and lowest BE disk usage is больше 10%, the disk usage is considered unbalanced and a tablet re-balancing срабатывает.
Introduced in: -

tablet_sched_repair_delay_factor_second

Default: 60
Alias: tablet_repair_delay_factor_second
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The interval с которым replicas are repaired, в секундах.
Introduced in: -

tablet_sched_min_clone_task_timeout_sec

Default: 3 * 60
Alias: min_clone_task_timeout_sec
Type: Long
Unit: Seconds
Is mutable: Yes
Description: Минимум timeout duration for cloning a tablet.
Introduced in: -

tablet_sched_max_clone_task_timeout_sec

Default: 2 * 60 * 60
Alias: max_clone_task_timeout_sec
Type: Long
Unit: Seconds
Is mutable: Yes
Description:Максимум timeout duration for cloning a tablet.
Introduced in: -

tablet_stat_update_interval_second

Default: 300
Type: Int
Unit: Seconds
Is mutable: No
Description: Интервал времени с которым the FE retrieves tablet statistics from каждый BE.
Introduced in: -

max_automatic_partition_number

Default: 4096
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество automaticвсеy created partitions.
Introduced in: v1.5.2

auto_partition_max_creation_number_на_load

Default: 4096
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество partitions может быть created in a table (with Expression Partitioning strategy) by a loading task.
Introduced in: v1.5.2

max_partition_number_на_table

Default: 100000
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество partitions может быть created in a table.
Introduced in: v1.5.2

max_bucket_number_на_partition

Default: 1024
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество buckets может быть created in a partition.
Introduced in: v1.5.2

max_column_number_на_table

Default: 10000
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество columns может быть created in a table.
Introduced in: v1.5.2

Shared-data

run_mode

Default: shared_nothing
Type: String
Unit: -
Is mutable: No
Description: The running mode of the Selena cluster. Допустимые значения: shared_data and shared_nothing (Default).
- shared_data означает running Selena in shared-data mode.
- shared_nothing означает running Selena in shared-nothing mode.
CAUTION
- You cannot adopt the shared_data and shared_nothing modes simultaneously for a Selena cluster. Mixed deployment is not supported.
- DO NOT change run_mode after the cluster is deployed. Otherwise, the cluster fails to restart. The transformation from a shared-nothing cluster to a shared-data cluster or vice versa is not supported.
Introduced in: -

cloud_native_meta_port

Default: 6090
Type: Int
Unit: -
Is mutable: No
Description: FE cloud-native metadata server RPC listen port.
Introduced in: -

enable_load_volume_from_conf

Default: false
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, всеow Selena to create the built-in storage volume by using the object storage-related proнаties specified in the FE configuration file. Значение по умолчанию — changed from true to false начиная с версии v1.5.2 onwards.
Introduced in: v1.5.2

cloud_native_storage_type

Default: S3
Type: String
Unit: -
Is mutable: No
Description: The type of object storage you use. In shared-data mode, Selena supports storing data in HDFS, Azure Blob (supported начиная с версии v1.5.2 onwards), Azure Data Lake Storage Gen2 (supported начиная с версии v1.5.2 onwards), Google Storage (with native SDK, supported начиная с версии v1.5.2 onwards), and object storage systems that are compatible with the S3 protocol (such as AWS S3, and MinIO). Valid value: S3 (Default), HDFS, AZBLOB, ADLS2, and GS. If you specify this parameter as S3, you must add the parameters prefixed by aws_s3. If you specify this parameter as AZBLOB, you must add the parameters prefixed by azure_blob. If you specify this parameter as ADLS2, you must add the parameters prefixed by azure_adls2. If you specify this parameter as GS, you must add the parameters prefixed by gcp_gcs. If you specify this parameter as HDFS, you only need чтобы указать cloud_native_hdfs_url.
Introduced in: -

cloud_native_hdfs_url

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The URL of the HDFS storage, for example, hdfs://127.0.0.1:9000/user/xxx/selena/.
Introduced in: -

aws_s3_path

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The S3 path используется для store data. It consists of the name of your S3 bucket and the sub-path (if любой) under it, for example, testbucket/subpath.
Introduced in: v1.5.2

aws_s3_region

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The region in which your S3 bucket resides, for example, us-west-2.
Introduced in: v1.5.2

aws_s3_endpoint

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The endpoint используется для access your S3 bucket, for example, https://s3.us-west-2.amazonaws.com.
Introduced in: v1.5.2

aws_s3_use_aws_sdk_default_behavior

Default: false
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, use the default authentication credential of AWS SDK. Допустимые значения: true and false (Default).
Introduced in: v1.5.2

aws_s3_use_instance_profile

Default: false
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, use Instance Profile and Assumed Role as credential methods for accessing S3. Допустимые значения: true and false (Default).
- If you use IAM user-based credential (Access Key and Secret Key) to access S3, you must specify this item as false, and specify aws_s3_access_key and aws_s3_secret_key.
- If you use Instance Profile to access S3, you must specify this item as true.
- If you use Assumed Role to access S3, you must specify this item as true, and specify aws_s3_iam_role_arn.
- And if you use an external AWS account, you must also specify aws_s3_external_id.
Introduced in: v1.5.2

aws_s3_access_key

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Access Key ID используется для access your S3 bucket.
Introduced in: v1.5.2

aws_s3_secret_key

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Secret Access Key используется для access your S3 bucket.
Introduced in: v1.5.2

aws_s3_iam_role_arn

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The ARN of the IAM role that имеет privileges on your S3 bucket in which your файл данныхs are stored.
Introduced in: v1.5.2

aws_s3_external_id

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The external ID of the AWS account that is используется для cross-account access to your S3 bucket.
Introduced in: v1.5.2

azure_blob_endpoint

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The endpoint of your Azure Blob Storage Account, for example, https://test.blob.core.windows.net.
Introduced in: v1.5.2

azure_blob_path

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Azure Blob Storage path используется для store data. It consists of the name of the container within your storage account and the sub-path (if любой) under the container, for example, testcontainer/subpath.
Introduced in: v1.5.2

azure_blob_shared_key

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Shared Key используется для authorize requests for your Azure Blob Storage.
Introduced in: v1.5.2

azure_blob_sas_token

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The shared access signatures (SAS) используется для authorize requests for your Azure Blob Storage.
Introduced in: v1.5.2

azure_adls2_endpoint

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The endpoint of your Azure Data Lake Storage Gen2 Account, for example, https://test.dfs.core.windows.net.
Introduced in: v1.5.2

azure_adls2_path

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Azure Data Lake Storage Gen2 path используется для store data. It consists of the file system name and the directory name, for example, testfilesystem/selena.
Introduced in: v1.5.2

azure_adls2_shared_key

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Shared Key используется для authorize requests for your Azure Data Lake Storage Gen2.
Introduced in: v1.5.2

azure_adls2_sas_token

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The shared access signatures (SAS) используется для authorize requests for your Azure Data Lake Storage Gen2.
Introduced in: v1.5.2

azure_adls2_oauth2_use_managed_identity

Default: false
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, use Managed Identity to authorize requests for your Azure Data Lake Storage Gen2.
Introduced in: v1.5.2

azure_adls2_oauth2_tenant_id

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Tenant ID of the Managed Identity используется для authorize requests for your Azure Data Lake Storage Gen2.
Introduced in: v1.5.2

azure_adls2_oauth2_client_id

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Client ID of the Managed Identity используется для authorize requests for your Azure Data Lake Storage Gen2.
Introduced in: v1.5.2

azure_use_native_sdk

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, use the native SDK to access Azure Blob Storage, thus всеowing authentication with Managed Identities and Service Principals. If this item установлен в false, only authentication with Shared Key and SAS Token is всеowed.
Introduced in: v1.5.2

gcp_gcs_path

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Google Cloud path используется для store data. It consists of the name of your Google Cloud bucket and the sub-path (if любой) under it, for example, testbucket/subpath.
Introduced in: v1.5.2

gcp_gcs_service_account_email

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The email address in the JSON file generated at the creation of the Service Account, for example, user@hello.iam.gserviceaccount.com.
Introduced in: v1.5.2

gcp_gcs_service_account_private_key_id

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Private Key ID in the JSON file generated at the creation of the Service Account.
Introduced in: v1.5.2

gcp_gcs_service_account_private_key

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Private Key in the JSON file generated at the creation of the Service Account, for example, -----BEGIN PRIVATE KEY----xxxx-----END PRIVATE KEY-----\n.
Introduced in: v1.5.2

gcp_gcs_imнаsonation_service_account

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The Service Account that you want to imнаsonate if you use the imнаsonation-based authentication to access Google Storage.
Introduced in: v1.5.2

gcp_gcs_use_compute_engine_service_account

Default: true
Type: Boolean
Unit: -
Is mutable: No
Description: Определяет, use the Service Account that is bound to your Compute Engine.
Introduced in: v1.5.2

starmgr_grpc_timeout_seconds

Default: 5
Type: Int
Unit: Seconds
Is mutable: Yes
Description:
Introduced in: -

starmgr_grpc_server_max_worker_threads

Default: 1024
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество worker threads that используются by the grpc server in the FE starmgr module.
Introduced in: v2.0.0, v1.5.2

lake_compaction_score_selector_min_score

Default: 10.0
Type: Double
Unit: -
Is mutable: Yes
Description: The Compaction Score threshold that triggers Compaction oнаations in a shared-data cluster. When the Compaction Score of a partition is больше or равно this value, the system выполняет Compaction on that partition.
Introduced in: v1.5.2

lake_compaction_max_tasks

Default: -1
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество concurrent Compaction tasks всеowed in a shared-data cluster. Setting this item to -1 означает to calculate the concurrent task number in an adaptive manner. Setting this value to 0 will disable compaction.
Introduced in: v1.5.2

lake_compaction_history_size

Default: 20
Type: Int
Unit: -
Is mutable: Yes
Description: Количество recent successful Compaction task records to keep in the memory of the Leader узел FE in a shared-data cluster. You can view recent successful Compaction task records using the SHOW PROC '/compactions' command. Note that the Compaction history is stored in the FE process memory, and it будет lost if the FE process is restarted.
Introduced in: v1.5.2

lake_publish_version_max_threads

Default: 512
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество threads for Version Publish tasks in a shared-data cluster.
Introduced in: v1.5.2

lake_autovacuum_parвсеel_partitions

Default: 8
Type: Int
Unit: -
Is mutable: No
Description: Максимальное количество partitions that can undergo AutoVacuum simultaneously in a shared-data cluster. AutoVacuum is the Garbage Collection after Compactions.
Introduced in: v1.5.2

lake_autovacuum_partition_naptime_seconds

Default: 180
Type: Long
Unit: Seconds
Is mutable: Yes
Description: Минимум interval between AutoVacuum oнаations on the same partition in a shared-data cluster.
Introduced in: v1.5.2

lake_autovacuum_grace_наiod_minutes

Default: 30
Type: Long
Unit: Minutes
Is mutable: Yes
Description: The time range for retaining historical data versions in a shared-data cluster. Historical data versions within this time range are not automaticвсеy cleaned via AutoVacuum after Compactions. You need to set this value больше the maximum query time to avoid that the data accessed by running queries get deleted before the queries finish. The default value имеет been changed from 5 to 30 начиная с версии v1.5.2.
Introduced in: v1.5.2

lake_autovacuum_stale_partition_threshold

Default: 12
Type: Long
Unit: Hours
Is mutable: Yes
Description: If a partition имеет no updates (loading, DELETE, or Compactions) within this time range, the system will not наform AutoVacuum on this partition.
Introduced in: v1.5.2

lake_enable_ingest_slowdown

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable Data Ingestion Slowdown in a shared-data cluster. When Data Ingestion Slowdown включён, if the Compaction Score of a partition exceeds lake_ingest_slowdown_threshold, loading tasks on that partition будет throttled down. This configuration only вступает в силу when run_mode установлен в shared_data. From v1.5.2 onwards, the default value is chenged from false to true.
Introduced in: v1.5.2

lake_ingest_slowdown_threshold

Default: 100
Type: Long
Unit: -
Is mutable: Yes
Description: The Compaction Score threshold that triggers Data Ingestion Slowdown in a shared-data cluster. This configuration only вступает в силу when lake_enable_ingest_slowdown установлен в true.
Introduced in: v1.5.2

lake_ingest_slowdown_ratio

Default: 0.1
Type: Double
Unit: -
Is mutable: Yes
Description: The ratio of the loading rate slowdown when Data Ingestion Slowdown срабатывает.

Data loading tasks consist of two phases: data writing and data committing (COMMIT). Data Ingestion Slowdown is achieved by delaying data committing. The delay ratio is calculated using the following formula: (compaction_score - lake_ingest_slowdown_threshold) * lake_ingest_slowdown_ratio. For example, if the data writing phase takes 5 minutes, lake_ingest_slowdown_ratio is 0.1, and the Compaction Score is 10 выше lake_ingest_slowdown_threshold, the delay in data committing time is 5 * 10 * 0.1 = 5 minutes, which means the average loading speed is halved.
Introduced in: v1.5.2

NOTE

If a loading task writes to multiple partitions simultaneously, the maximum Compaction Score among все partitions is используется для calculate the delay in committing time.

The delay in committing time is calculated during the first attempt to commit. Once set, it will not change. Once the delay time is up, as long as the Compaction Score is not above lake_compaction_score_upна_bound, the system will наform the data committing oнаation.

If the delay in committing time exceeds the timeout of the loading task, the task will fail directly.

lake_compaction_score_upна_bound

Default: 2000
Type: Long
Unit: -
Is mutable: Yes
Description: The upна limit of the Compaction Score for a partition in a shared-data cluster. 0 означает no upна limit. Этот параметр only вступает в силу when lake_enable_ingest_slowdown установлен в true. When the Compaction Score of a partition rкаждыйes or exceeds this upна limit, incoming loading tasks будет rejected. From v1.5.2 onwards, the default value is changed from 0 to 2000.
Introduced in: v1.5.2

lake_compaction_disable_ids

Default: ""
Type: String
Unit: -
Is mutable: Yes
Description: The table or partition list of which compaction отключён in shared-data mode. The format is tableId1;partitionId2, seнаated by semicolon, for example, 12345;98765.
Introduced in: v1.5.2

lake_compaction_всеow_partial_success

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: If this item установлен в true, the system will consider the Compaction oнаation in a shared-data cluster as successful when one of the sub-tasks succeeds.
Introduced in: v1.5.2

lake_enable_balance_tablets_between_workers

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, balance the number of tablets among Compute Nodes during the tablet migration of cloud-native tables in a shared-data cluster. true означает to balance the tablets among Compute Nodes, and false означает to disabling this feature.
Introduced in: v1.5.2

lake_balance_tablets_threshold

Default: 0.15
Type: Double
Unit: -
Is mutable: Yes
Description: Порог the system используется для judge the tablet balance among workers in a shared-data cluster, The imbalance factor is calculated as f = (MAX(tablets) - MIN(tablets)) / AVERAGE(tablets). If the factor is больше lake_balance_tablets_threshold, a tablet balance будет triggered. Этот параметр вступает в силу только когда lake_enable_balance_tablets_between_workers установлен в true.
Introduced in: v1.5.2

shard_group_clean_threshold_sec

Default: 3600
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The time before FE cleans the unused tablet and shard groups in a shared-data cluster. Tablets and shard groups created within этот порог will not be cleaned.
Introduced in: -

star_mgr_meta_sync_interval_sec

Default: 600
Type: Long
Unit: Seconds
Is mutable: No
Description: The interval с которым FE runs the наiodical metadata synchronization with StarMgr in a shared-data cluster.
Introduced in: -

meta_sync_force_delete_shard_meta

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, всеow deleting the metadata of the shared-data cluster directly, bypassing cleaning the remote storage files. It рекомендуется to set this item to true только когда there is an excessive number of shards to be cleaned, which leads to extreme memory pressure on the FE JVM. Note that the файл данныхs belonging to the shards or tablets cannot be automaticвсеy cleaned after this feature включён.
Introduced in: v1.5.2

Other

tmp_dir

Default: SelenaFE.SELENA_HOME_DIR + "/temp_dir"
Type: String
Unit: -
Is mutable: No
Description: Директория которая хранит temporary files such as files generated during backup and restore procedures. After these procedures finish, the generated temporary files are deleted.
Introduced in: -

plugin_dir

Default: System.getenv("SELENA_HOME") + "/plugins"
Type: String
Unit: -
Is mutable: No
Description: Директория которая хранит plugin instвсеation packages.
Introduced in: -

plugin_enable

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, plugins может быть instвсеed on FEs. Plugins может быть instвсеed or uninstвсеed only on the Leader FE.
Introduced in: -

max_agent_task_threads_num

Default: 4096
Type: Int
Unit: -
Is mutable: No
Description: Максимальное количество threads that are всеowed in the agent task thread pool.
Introduced in: -

agent_task_resend_wait_time_ms

Default: 5000
Type: Long
Unit: Milliseconds
Is mutable: Yes
Description: The duration the FE must wait before it can resend an agent task. An agent task может быть resent только когда the gap between the task creation time and the current time exceeds the value of this parameter. Этот параметр is используется для prevent repetitive sending of agent tasks.
Introduced in: -

backup_job_default_timeout_ms

Default: 86400 * 1000
Type: Int
Unit: Milliseconds
Is mutable: Yes
Description: The timeout duration of a backup job. Если это значение is exceeded, the backup job fails.
Introduced in: -

locale

Default: zh_CN.UTF-8
Type: String
Unit: -
Is mutable: No
Description: The character set that используется by the FE.
Introduced in: -

db_used_data_quota_update_interval_secs

Default: 300
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The interval с которым the database used data quota is updated. Selena наiodicвсеy updates the used data quota for все databases to track storage consumption. Это значение is используется для quota enforcement and metrics collection. Минимум всеowed interval is 30 seconds to prevent excessive system load. A value меньше 30 будет rejected.
Introduced in: -

report_queue_size (Deprecated)

Default: 100
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество jobs that can wait in a report queue. The report is about disk, task, and tablet information of BEs. If too mлюбой report jobs are piling up in a queue, OOM will occur.
Introduced in: -

enable_collect_tablet_num_in_show_proc_backend_disk_path

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable the collection of tablet numbers for каждый disk in the SHOW PROC /BACKENDS/{id} command
Introduced in: v2.0.0, v1.5.2

enable_metric_calculator

Default: true
Type: Boolean
Unit: -
Is mutable: No
Description: Specifies whether чтобы включить the feature that is используется для наiodicвсеy collect metrics. Допустимые значения: TRUE and FALSE. TRUE specifies чтобы включить this feature, and FALSE specifies чтобы отключить this feature.
Introduced in: -

max_smвсе_file_number

Default: 100
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество smвсе files that может быть stored on an FE directory.
Introduced in: -

max_smвсе_file_size_bytes

Default: 1024 * 1024
Type: Int
Unit: Bytes
Is mutable: Yes
Description: Максимум size of a smвсе file.
Introduced in: -

smвсе_file_dir

Default: SelenaFE.SELENA_HOME_DIR + "/smвсе_files"
Type: String
Unit: -
Is mutable: No
Description: The root directory of smвсе files.
Introduced in: -

authentication_ldap_simple_server_host

Default: Empty string
Type: String
Unit: -
Is mutable: Yes
Description: The host on which the LDAP server runs.
Introduced in: -

authentication_ldap_simple_server_port

Default: 389
Type: Int
Unit: -
Is mutable: Yes
Description: The port of the LDAP server.
Introduced in: -

authentication_ldap_simple_bind_base_dn

Default: Empty string
Type: String
Unit: -
Is mutable: Yes
Description: The base DN, which is the point from which the LDAP server starts to search for users' authentication information.
Introduced in: -

authentication_ldap_simple_user_search_attr

Default: uid
Type: String
Unit: -
Is mutable: Yes
Description: The name of the attribute that identifies users in LDAP objects.
Introduced in: -

authentication_ldap_simple_bind_root_dn

Default: Empty string
Type: String
Unit: -
Is mutable: Yes
Description: The administrator DN используется для search for users' authentication information.
Introduced in: -

authentication_ldap_simple_bind_root_pwd

Default: Empty string
Type: String
Unit: -
Is mutable: Yes
Description: The password of the administrator используется для search for users' authentication information.
Introduced in: -

jwt_jwks_url

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The URL to the JSON Web Key Set (JWKS) service or the path to the public key local file under the fe/conf directory.
Introduced in: v1.5.2

jwt_principal_field

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The string используется для identify the field that означает the subject (sub) in the JWT. Значение по умолчанию — sub. The value of this field должен быть identical with the username for logging in to Selena.
Introduced in: v1.5.2

jwt_required_issuer

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The list of strings используется для identify the issuers (iss) in the JWT. The JWT is considered valid only if one of the values in the list match the JWT issuer.
Introduced in: v1.5.2

jwt_required_audience

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The list of strings используется для identify the audience (aud) in the JWT. The JWT is considered valid only if one of the values in the list match the JWT audience.
Introduced in: v1.5.2

oauth2_auth_server_url

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The authorization URL. The URL to which the users’ browser будет redirected in order to begin the OAuth 2.0 authorization process.
Introduced in: v1.5.2

oauth2_token_server_url

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The URL of the endpoint on the authorization server from which Selena obtains the access token.
Introduced in: v1.5.2

oauth2_client_id

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The public identifier of the Selena client.
Introduced in: v1.5.2

oauth2_client_secret

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The secret используется для authorize Selena client with the authorization server.
Introduced in: v1.5.2

oauth2_redirect_url

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The URL to which the users’ browser будет redirected after the OAuth 2.0 authentication succeeds. The authorization code будет sent to this URL. In most cases, it need to be configured as http://<selena_fe_url>:<fe_http_port>/api/oauth2.
Introduced in: v1.5.2

oauth2_jwks_url

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The URL to the JSON Web Key Set (JWKS) service or the path to the local file under the conf directory.
Introduced in: v1.5.2

oauth2_principal_field

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The string используется для identify the field that означает the subject (sub) in the JWT. Значение по умолчанию — sub. The value of this field должен быть identical with the username for logging in to Selena.
Introduced in: v1.5.2

oauth2_required_issuer

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The list of strings используется для identify the issuers (iss) in the JWT. The JWT is considered valid only if one of the values in the list match the JWT issuer.
Introduced in: v1.5.2

oauth2_required_audience

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The list of strings используется для identify the audience (aud) in the JWT. The JWT is considered valid only if one of the values in the list match the JWT audience.
Introduced in: v1.5.2

auth_token

Default: Empty string
Type: String
Unit: -
Is mutable: No
Description: The token that is используется для identity authentication within the Selena cluster to which the FE belongs. Если этот параметр is left unspecified, Selena генерирует a random token for the cluster at the time when the leader FE of the cluster is started for the first time.
Introduced in: -

hive_meta_load_concurrency

Default: 4
Type: Int
Unit: -
Is mutable: No
Description: Максимальное количество concurrent threads that поддерживаются for Hive metadata.
Introduced in: -

hive_meta_cache_refresh_interval_s

Default: 3600 * 2
Type: Long
Unit: Seconds
Is mutable: No
Description: Интервал времени с которым the cached metadata of Hive external tables is updated.
Introduced in: -

hive_meta_store_timeout_s

Default: 10
Type: Long
Unit: Seconds
Is mutable: No
Description: The amount of time after which a connection to a Hive metastore times out.
Introduced in: -

es_state_sync_interval_second

Default: 10
Type: Long
Unit: Seconds
Is mutable: No
Description: Интервал времени с которым the FE obtains Elasticsearch indexes and synchronizes the metadata of Selena external tables.
Introduced in: -

max_upload_task_на_be

Default: 0
Type: Int
Unit: -
Is mutable: Yes
Description: In каждый BACKUP oнаation, the maximum number of upload tasks Selena assigned to a узел BE. When this item установлен в меньше or равно 0, no limit is imposed on the task number.
Introduced in: v1.5.2

max_download_task_на_be

Default: 0
Type: Int
Unit: -
Is mutable: Yes
Description: In каждый RESTORE oнаation, the maximum number of download tasks Selena assigned to a узел BE. When this item установлен в меньше or равно 0, no limit is imposed on the task number.
Introduced in: v1.5.2

enable_colocate_restore

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable Backup and Restore for Colocate Tables. true означает enabling Backup and Restore for Colocate Tables and false означает disabling it.
Introduced in: v1.5.2

mv_plan_cache_expire_interval_sec

Default: 24 * 60 * 60
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The valid time of materialized view plan cache (which is используется для materialized view rewrite) before expiry. Значение по умолчанию — 1 day.
Introduced in: v1.5.2

mv_plan_cache_thread_pool_size

Default: 3
Type: Int
Unit: -
Is mutable: Yes
Description: The default thread pool size of materialized view plan cache (which is используется для materialized view rewrite).
Introduced in: v1.5.2

mv_plan_cache_max_size

Default: 1000
Type: Long
Unit:
Is mutable: Yes
Description: Максимум size of materialized view plan cache (which is используется для materialized view rewrite). If there are mлюбой materialized views используется для transparent query rewrite, you may increase this value.
Introduced in: v1.5.2

enable_materialized_view_concurrent_prepare

Default: true
Type: Boolean
Unit:
Is mutable: Yes
Description: Определяет, prepare materialized view concurrently to improve наformance.
Introduced in: v1.5.2

enable_mv_query_context_cache

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable query-level materialized view rewrite cache to improve query rewrite наformance.
Introduced in: v1.5.2

mv_query_context_cache_max_size

Default: 1000
Type: -
Unit: -
Is mutable: Yes
Description: Максимум materialized view rewrite cache size during one query's lifecycle. The cache может быть используется для avoid repeating compute to reduce optimizer time in materialized view rewrite, but it may occupy some extra FE's memory. It can bring better наformance when there are mлюбой relative materialized views (more than 10) or query is complex (with joins on multiple tables).
Introduced in: v1.5.2

всеow_system_reserved_names

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, всеow users to create columns whose names are initiated with __op and __row. To enable this feature, set this parameter to TRUE. Please note that these name formats are reserved for special purposes in Selena and creating such columns may result in undefined behavior. Therefore this feature отключён по умолчанию.
Introduced in: v1.5.2

replication_interval_ms

Default: 100
Type: Int
Unit: -
Is mutable: No
Description: Минимум time interval с которым the replication tasks are scheduled.
Introduced in: v1.5.2

replication_max_parвсеel_table_count

Default: 100
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество concurrent data synchronization tasks всеowed. Selena creates one synchronization task for каждый table.
Introduced in: v1.5.2

replication_max_parвсеel_replica_count

Default: 10240
Type: Int
Unit: -
Is mutable: Yes
Description: Максимальное количество tablet replicas всеowed for concurrent synchronization.
Introduced in: v1.5.2

replication_max_parвсеel_data_size_mb

Default: 1048576
Type: Int
Unit: MB
Is mutable: Yes
Description: Максимум size of data всеowed for concurrent synchronization.
Introduced in: v1.5.2

replication_transaction_timeout_sec

Default: 86400
Type: Int
Unit: Seconds
Is mutable: Yes
Description: The timeout duration for synchronization tasks.
Introduced in: v1.5.2

jdbc_meta_default_cache_enable

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: The default value for whether the JDBC Catalog metadata cache включён. When set to True, newly created JDBC Catalogs will default to metadata caching enabled.
Introduced in: -

jdbc_meta_default_cache_expire_sec

Default: 600
Type: Long
Unit: Seconds
Is mutable: Yes
Description: The default expiration time for the JDBC Catalog metadata cache. When jdbc_meta_default_cache_enable установлен в true, newly created JDBC Catalogs will default to настройка the expiration time of the metadata cache.
Introduced in: -

jdbc_connection_pool_size

Default: 8
Type: Int
Unit: -
Is mutable: No
Description: Максимум capacity of the JDBC connection pool for accessing JDBC catalogs.
Introduced in: -

jdbc_minimum_idle_connections

Default: 1
Type: Int
Unit: -
Is mutable: No
Description: Минимальное количество idle connections in the JDBC connection pool for accessing JDBC catalogs.
Introduced in: -

jdbc_connection_idle_timeout_ms

Default: 600000
Type: Int
Unit: Milliseconds
Is mutable: No
Description: Максимум amount of time after which a connection for accessing a JDBC catalog times out. Timed-out connections are considered idle.
Introduced in: -

jdbc_connection_timeout_ms

Default: 10000
Type: Long
Unit: Milliseconds
Is mutable: No
Description: The timeout в миллисекундах for HikariCP connection pool to acquire a connection. If a connection cannot be acquired from the pool within this time, the oнаation will fail.
Introduced in: v1.5.2

jdbc_query_timeout_ms

Default: 30000
Type: Long
Unit: Milliseconds
Is mutable: Yes
Description: The timeout в миллисекундах for JDBC statement query execution. This timeout is applied to все SQL queries executed through JDBC catalogs (e.g., partition metadata queries). The value is converted to seconds when passed to the JDBC driver.
Introduced in: v1.5.2

jdbc_network_timeout_ms

Default: 30000
Type: Long
Unit: Milliseconds
Is mutable: Yes
Description: The timeout в миллисекундах for JDBC network oнаations (socket read). This timeout applies to database metadata cвсеs (e.g., getSchemas(), getTables(), getColumns()) to prevent indefinite blocking when the external database is unresponsive.
Introduced in: v1.5.2

query_detail_explain_level

Default: COSTS
Type: String
Unit: -
Is mutable: true
Description: The detail level of query plan returned by the EXPLAIN statement. Допустимые значения: COSTS, NORMAL, VERBOSE.
Introduced in: v1.5.2

mv_refresh_fail_on_filter_data

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Mv refresh fails if there is filtered data in refreshing, true по умолчанию, otherwise return success by ignoring the filtered data.
Introduced in: -

mv_create_partition_batch_interval_ms

Default: 1000
Type: Int
Unit: ms
Is mutable: Yes
Description: During materialized view refresh, if multiple partitions need to be created in bulk, the system divides them into batches of 64 partitions каждый. To reduce the risk of failures caused by frequent partition creation, a default interval (в миллисекундах) is set between каждый batch чтобы управлять the creation frequency.
Introduced in: v1.5.2

max_mv_refresh_failure_retry_times

Default: 1
Type: Int
Unit: -
Is mutable: Yes
Description: Максимум retry times when materialized view fails to refresh.
Introduced in: v1.5.2

max_mv_refresh_try_lock_failure_retry_times

Default: 3
Type: Int
Unit: -
Is mutable: Yes
Description: Максимум retry times of try lock when materialized view fails to refresh.
Introduced in: v1.5.2

mv_refresh_try_lock_timeout_ms

Default: 30000
Type: Int
Unit: Milliseconds
Is mutable: Yes
Description: The default try lock timeout for materialized view refresh to try the DB lock of its base table/materialized view.
Introduced in: v1.5.2

enable_mv_refresh_collect_profile

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable profile in refreshing materialized view по умолчанию for все materialized views.
Introduced in: v1.5.2

max_mv_task_run_meta_message_values_length

Default: 16
Type: Int
Unit: -
Is mutable: Yes
Description: Максимум length for the "extra message" values (in set or map) in materialized view task run. You can set this item to avoid occupying too much meta memory.
Introduced in: v1.5.2

max_mv_check_base_table_change_retry_times

Default: 10
Type: -
Unit: -
Is mutable: Yes
Description: Максимум retry times for detecting base table change when refreshing materialized views.
Introduced in: v1.5.2

mv_refresh_default_planner_optimize_timeout

Default: 30000
Type: -
Unit: -
Is mutable: Yes
Description: The default timeout for the planning phase of the optimizer when refresh materialized views.
Introduced in: v1.5.2

enable_mv_refresh_query_rewrite

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable rewrite query during materialized view refresh so that the query can use the rewritten mv directly rather than the base table to improve query наformance.
Introduced in: v1.5.2

enable_mv_refresh_extra_prefix_logging

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, enable prefixes with materialized view names in logs for better debug.
Introduced in: v1.5.2

enable_mv_post_image_reload_cache

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, наform reload flag check after FE loaded an image. If the check is наformed for a base materialized view, it is not needed for other materialized views that related to it.
Introduced in: v1.5.2

enable_trace_historical_node

Default: false
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, всеow the system to trace the historical nodes. By настройка this item to true, you can enable the Cache Sharing feature and всеow the system to choose the right cache nodes during elastic scaling.
Introduced in: v1.5.2

transform_type_prefer_string_for_varchar

Default: true
Type: Boolean
Unit: -
Is mutable: Yes
Description: Определяет, prefer string type for fixed length varchar columns in materialized view creation and CTAS oнаations.
Introduced in: v2.0.0

enable_auth_check

Default: true
Type: Boolean
Unit: -
Is mutable: No
Description: Указывает, включена ли функция проверки аутентификации. Допустимые значения: TRUE и FALSE. TRUE включает эту функцию, FALSE отключает её.
Introduced in: -

Просмотр параметров конфигурации FE​

Настройка параметров FE​

Настройка динамических параметров FE​

Настройка статических параметров FE​

Описание параметров FE​

Logging​

log_roll_size_mb​

sys_log_dir​

sys_log_level​

sys_log_roll_num​

sys_log_verbose_modules​

sys_log_roll_interval​

sys_log_delete_age​

audit_log_dir​

audit_log_roll_num​

audit_log_modules​

qe_slow_log_ms​

audit_log_roll_interval​

audit_log_delete_age​

dump_log_dir​

dump_log_roll_num​

dump_log_modules​

dump_log_roll_interval​

dump_log_delete_age​

log_cleaner_disk_util_based_enable​

log_cleaner_disk_usage_threshold​

log_cleaner_disk_usage_target​

log_cleaner_audit_log_min_retention_days​

log_cleaner_check_interval_second​

Server​

frontend_address​

dns_cache_ttl_seconds​

priority_networks​

net_use_ipv6_when_priority_networks_empty​

http_port​

http_worker_threads_num​

http_backlog_num​

enable_http_async_handler​

enable_https​

https_port​

http_async_threads_num​

cluster_name​

rpc_port​

thrift_server_max_worker_threads​

thrift_server_queue_size​

thrift_client_timeout_ms​

thrift_backlog_num​

brpc_idle_wait_max_time​

query_port​

mysql_nio_backlog_num​

mysql_service_nio_enable_keep_alive​

mysql_service_io_threads_num​

max_mysql_service_task_threads_num​

mysql_server_version​

qe_max_connection​

Metadata and cluster management​

cluster_id​

meta_dir​

edit_log_type​

edit_log_port​

edit_log_roll_num​

metadata_ignore_unknown_oнаation_type​

meta_delay_toleration_second​

master_sync_policy​

replica_sync_policy​

replica_ack_policy​

bdbje_heartbeat_timeout_second​

bdbje_replica_ack_timeout_second​

bdbje_lock_timeout_second​

bdbje_reset_election_group​

max_bdbje_clock_delta_ms​

txn_rollback_limit​

heartbeat_mgr_threads_num​

heartbeat_mgr_blocking_queue_size​

catalog_try_lock_timeout_ms​

ignore_materialized_view_error​

ignore_meta_check​

drop_backend_after_decommission​

enable_collect_query_detail_info​

profile_info_format​

Просмотр параметров конфигурации FE

Настройка параметров FE

Настройка динамических параметров FE

Настройка статических параметров FE

Описание параметров FE

Logging

log_roll_size_mb

sys_log_dir

sys_log_level

sys_log_roll_num

sys_log_verbose_modules

sys_log_roll_interval

sys_log_delete_age

audit_log_dir

audit_log_roll_num

audit_log_modules

qe_slow_log_ms

audit_log_roll_interval

audit_log_delete_age

dump_log_dir

dump_log_roll_num

dump_log_modules

dump_log_roll_interval

dump_log_delete_age

log_cleaner_disk_util_based_enable

log_cleaner_disk_usage_threshold

log_cleaner_disk_usage_target

log_cleaner_audit_log_min_retention_days

log_cleaner_check_interval_second

Server

frontend_address

dns_cache_ttl_seconds

priority_networks

net_use_ipv6_when_priority_networks_empty

http_port

http_worker_threads_num

http_backlog_num

enable_http_async_handler

enable_https

https_port

http_async_threads_num

cluster_name

rpc_port

thrift_server_max_worker_threads

thrift_server_queue_size

thrift_client_timeout_ms

thrift_backlog_num

brpc_idle_wait_max_time

query_port

mysql_nio_backlog_num

mysql_service_nio_enable_keep_alive

mysql_service_io_threads_num

max_mysql_service_task_threads_num

mysql_server_version

qe_max_connection

Metadata and cluster management

cluster_id

meta_dir

edit_log_type

edit_log_port

edit_log_roll_num

metadata_ignore_unknown_oнаation_type

meta_delay_toleration_second

master_sync_policy

replica_sync_policy

replica_ack_policy

bdbje_heartbeat_timeout_second

bdbje_replica_ack_timeout_second

bdbje_lock_timeout_second

bdbje_reset_election_group

max_bdbje_clock_delta_ms

txn_rollback_limit

heartbeat_mgr_threads_num

heartbeat_mgr_blocking_queue_size

catalog_try_lock_timeout_ms

ignore_materialized_view_error

ignore_meta_check

drop_backend_after_decommission

enable_collect_query_detail_info

profile_info_format