YDB Cluster Configuration
The cluster configuration is specified in the YAML file passed in the --yaml-config parameter when the cluster nodes are run. This article provides an overview of the main configuration sections and links to detailed documentation for each section.
Each configuration section serves a specific purpose in defining how the YDB cluster operates, from hardware resource allocation to security settings and feature flags. The configuration is organized into logical groups that correspond to different aspects of cluster management and operation.
Configuration Sections
The following top-level configuration sections are available, listed in alphabetical order:
|
Section |
Required |
Description |
|
Yes |
CPU resource allocation across actor system pools |
|
|
No |
Authentication and authorization settings |
|
|
No |
Static cluster group configuration for system tablets |
|
|
No |
Client certificate authentication |
|
|
No |
Cluster domain configuration including Blob Storage and State Storage |
|
|
No |
Feature flags to enable or disable specific YDB features |
|
|
No |
Health check service thresholds and timeout settings |
|
|
No |
Hive component configuration for tablet management |
|
|
No |
Typical host configurations for cluster nodes |
|
|
Yes |
Static cluster nodes configuration |
|
|
No |
Logging configuration and parameters |
|
|
No |
Memory allocation and limits for database components |
|
|
No |
Stable node names configuration |
|
|
No |
Resource broker for controlling CPU and memory consumption |
|
|
No |
Security configuration settings |
|
|
No |
TLS configuration for secure connections |
Practical Guidelines
While this documentation section focuses on complete reference documentation for available settings, practical recommendations on what to tune and when can be found in the following places:
-
As part of the initial YDB cluster deployment:
-
As part of troubleshooting
-
As part of security hardening
Sample cluster configurations
You can find model cluster configurations for deployment in the repository. Check them out before deploying a cluster.