--- metadata: - name: generator content: Diplodoc Platform v5.52.0 alternate: - https://ydb.tech/docs/en/devops/deployment-options/ansible/initial-deployment.md?version=v25.3 - href: en/devops/deployment-options/ansible/initial-deployment.md type: text/markdown title: Markdown version - href: ../../../llms.txt type: text/markdown title: llms.txt sourcePath: en/core/devops/deployment-options/ansible/initial-deployment.md --- > **Documentation Index:** Fetch the complete configuration index at https://ydb.tech/docs/en/llms.txt # Deploying YDB Cluster with Ansible This guide outlines the process of deploying a YDB cluster on a group of servers using [Ansible](https://www.ansible.com/). This is the recommended approach for bare-metal or virtual machine environments. ## Prerequisites ### Server Setup The recommended setup to get started is 3 servers with 3 disk drives for user data each. For reliability purposes, each server should have as independent infrastructure as possible: they'd better be each in a separate datacenter or availability zone, or at least in different server racks. For large-scale setups, it is recommended to use at least 9 servers for highly available clusters (`mirror-3-dc`) or 8 servers for single-datacenter clusters (`block-4-2`). In these cases, servers can have only one disk drive for user data each, but they'd better have an additional small drive for the operating system. You can learn about redundancy models available in YDB from the [YDB Cluster Topology](https://ydb.tech/docs/en/concepts/topology.md?version=v25.3) article. During operation, the cluster can be [expanded](https://ydb.tech/docs/en/devops/configuration-management/configuration-v2/cluster-expansion.md?version=v25.3) without suspending user access to the databases. {% note info %} Recommended server requirements: * 16 CPUs (calculated based on the utilization of 8 CPUs by the storage node and 8 CPUs by the dynamic node). * 16 GB RAM (recommended minimum RAM). * Additional SSD drives for data, at least 120 GB each. * SSH access. * Network connectivity between machines in the cluster. * OS: Ubuntu 18+, Debian 9+. * Internet access is needed to update repositories and download necessary packages. See [YDB System Requirements and Recommendations](https://ydb.tech/docs/en/devops/concepts/system-requirements.md?version=v25.3) for more details. {% endnote %} If you plan to use virtual machines in a public cloud provider, consider following [Deploy Infrastructure for YDB Cluster using Terraform](https://ydb.tech/docs/en/devops/deployment-options/ansible/preparing-vms-with-terraform.md?version=v25.3). ### Software Setup To work with the project on a local (intermediate or installation) machine, you will need: - Python 3 version 3.10+ - Ansible core version 2.15.2 or higher - A working directory on a server with SSH access to all cluster servers {% note tip %} It is recommended to keep the working directory and all files created during this guide in a [VCS](https://en.wikipedia.org/wiki/Version_control) repository such as [Git](https://git-scm.com/). If multiple DevOps engineers will be working with the cluster to be deployed, they should collaborate in the same repository. {% endnote %} If Ansible is already installed, you can move on to the step ["Configuring the Ansible project"](#ansible-project-setup). If Ansible is not yet installed, install it using one of the following methods: {% cut "Installing Ansible globally" %} Using Ubuntu 22.04 LTS as an example: * Update the apt package list with `sudo apt-get update`. * Upgrade packages with `sudo apt-get upgrade`. * Install the `software-properties-common` package to manage your distribution's software sources – `sudo apt install software-properties-common`. * Add a new PPA to apt – `sudo add-apt-repository --yes --update ppa:ansible/ansible`. * Install Ansible – `sudo apt-get install ansible-core` (note that installing just `ansible` will lead to an unsuitable outdated version). * Check the Ansible core version – `ansible --version` Refer to [Ansible Installation Guide](https://docs.ansible.com/ansible/latest/installation_guide/index.html) for more details and other installation options. {% endcut %} {% cut "Installing Ansible in a Python virtual environment" %} * Update the apt package list – `sudo apt-get update`. * Install the `venv` package for Python3 – `sudo apt-get install python3-venv` * Create a directory where the virtual environment will be created and where the playbooks will be downloaded. For example, `mkdir venv-ansible`. * Create a Python virtual environment – `python3 -m venv venv-ansible`. * Activate the virtual environment – `source venv-ansible/bin/activate`. All further actions with Ansible are performed inside the virtual environment. You can exit it with the command `deactivate`. * Install the recommended version of Ansible using the command `pip3 install -r requirements.txt`, while in the root directory of the downloaded repository. * Check the Ansible core version – `ansible --version` {% endcut %} ## Configure the Ansible Project {#ansible-project-setup} ### Install YDB Ansible Playbooks {% list tabs %} - Via requirements.yaml ```bash $ cat < requirements.yaml roles: [] collections: - name: git+https://github.com/ydb-platform/ydb-ansible type: git version: latest EOF $ ansible-galaxy install -r requirements.yaml ``` - One-time ```bash $ ansible-galaxy collection install git+https://github.com/ydb-platform/ydb-ansible.git,latest ``` {% endlist %} ### Configure Ansible Create `ansible.cfg` with Ansible configuration that makes sense for your environment. Refer to [Ansible Configuration Reference](https://docs.ansible.com/ansible/latest/reference_appendices/config.html) for more details on this. The further guide assumes that the `./inventory` subdirectory of the working directory is configured to be used for inventory files. {% cut "Example starter ansible.cfg" %} ```ini [defaults] conditional_bare_variables = False force_handlers = True gathering = explicit interpreter_python = /usr/bin/python3 inventory = ./inventory pipelining = True private_role_vars = True timeout = 5 verbosity = 1 log_path = ./ydb.log [ssh_connection] retries = 5 timeout = 60 ``` {% endcut %} ### Create the Primary Inventory File {#inventory-create} Create a `inventory/50-inventory.yaml` file using one of the templates below depending on the chosen [YDB cluster topology](https://ydb.tech/docs/en/concepts/topology.md?version=v25.3): {% list tabs %} - 3 nodes ```yaml all: children: ydb: # Servers hosts: static-node-1.ydb-cluster.com: location: data_center: 'zone-a' static-node-2.ydb-cluster.com: location: data_center: 'zone-b' static-node-3.ydb-cluster.com: location: data_center: 'zone-c' vars: # Ansible ansible_user: ubuntu ansible_ssh_private_key_file: "~/ydb" # System system_timezone: UTC system_ntp_servers: pool.ntp.org # Nodes ydb_version: "25.1.1" ydb_storage_node_cores: 8 ydb_database_node_cores: 8 # Storage ydb_database_storage_groups: 8 ydb_disks: - name: /dev/vdb label: ydb_disk_1 - name: /dev/vdc label: ydb_disk_2 - name: /dev/vdd label: ydb_disk_3 ydb_allow_format_drives: true # replace with false after the initial setup # Database ydb_user: root ydb_domain: Root ydb_database_name: database ydb_config: erasure: mirror-3-dc fail_domain_type: disk default_disk_type: SSD security_config: enforce_user_token_requirement: true ``` - Cross-datacenter ```yaml all: children: ydb: # Servers hosts: static-node-1.ydb-cluster.com: location: data_center: 'zone-a' rack: 'rack-1' static-node-2.ydb-cluster.com: location: data_center: 'zone-a' rack: 'rack-2' static-node-3.ydb-cluster.com: location: data_center: 'zone-a' rack: 'rack-3' static-node-4.ydb-cluster.com: location: data_center: 'zone-b' rack: 'rack-4' static-node-5.ydb-cluster.com: location: data_center: 'zone-b' rack: 'rack-5' static-node-6.ydb-cluster.com: location: data_center: 'zone-b' rack: 'rack-6' static-node-7.ydb-cluster.com: location: data_center: 'zone-c' rack: 'rack-7' static-node-8.ydb-cluster.com: location: data_center: 'zone-c' rack: 'rack-8' static-node-9.ydb-cluster.com: location: data_center: 'zone-c' rack: 'rack-9' vars: # Ansible ansible_user: ubuntu ansible_ssh_private_key_file: "~/ydb" # System system_timezone: UTC system_ntp_servers: pool.ntp.org # Nodes ydb_version: "25.1.1" ydb_storage_node_cores: 8 ydb_database_node_cores: 8 # Storage ydb_database_storage_groups: 8 ydb_disks: - name: /dev/vdb label: ydb_disk_1 ydb_allow_format_drives: true # replace with false after the initial setup # Database ydb_user: root ydb_domain: Root ydb_database_name: database ydb_config: erasure: mirror-3-dc default_disk_type: SSD security_config: enforce_user_token_requirement: true ``` - Single datacenter ```yaml all: children: ydb: # Servers hosts: static-node-1.ydb-cluster.com: location: rack: 'rack-1' static-node-2.ydb-cluster.com: location: rack: 'rack-2' static-node-3.ydb-cluster.com: location: rack: 'rack-3' static-node-4.ydb-cluster.com: location: rack: 'rack-4' static-node-5.ydb-cluster.com: location: rack: 'rack-5' static-node-6.ydb-cluster.com: location: rack: 'rack-6' static-node-7.ydb-cluster.com: location: rack: 'rack-7' static-node-8.ydb-cluster.com: location: rack: 'rack-8' vars: # Ansible ansible_user: ubuntu ansible_ssh_private_key_file: "~/ydb" # System system_timezone: UTC system_ntp_servers: pool.ntp.org # Nodes ydb_version: "25.1.1" ydb_storage_node_cores: 8 ydb_database_node_cores: 8 # Storage ydb_database_storage_groups: 8 ydb_disks: - name: /dev/vdb label: ydb_disk_1 ydb_allow_format_drives: true # replace with false after the initial setup # Database ydb_user: root ydb_domain: Root ydb_database_name: database ydb_config: erasure: block-4-2 default_disk_type: SSD security_config: enforce_user_token_requirement: true ``` {% endlist %} Mandatory settings to adjust for your environment in the chosen template: 1. **Server hostnames.** Replace `static-node-*.ydb-cluster.com` in `all.children.ydb.hosts` with the real [FQDNs](https://en.wikipedia.org/wiki/Fully_qualified_domain_name). 2. **Server locations.** The names in `data_center` and `rack` in `all.children.ydb.hosts.location` are arbitrary, but they should match between servers only if they are indeed located in the same datacenter (or availability zone) and rack, respectively. 3. **Filesystem paths to block devices** in `all.children.ydb.vars.ydb_disks`. The template assumes `/dev/vda` is for the operating system and the following disks like `/dev/vdb` are for YDB storage layer. Disk labels are created by the playbooks automatically and their names can be arbitrary. 4. **Ansible-related settings** with `all.children.ydb.ansible_` prefix like username and private key to use for `ssh`. Add more of them like `ansible_ssh_common_args` as necessary. Recommended settings to adjust: * `ydb_domain`. It will be the first path component for all [scheme objects](https://ydb.tech/docs/en/concepts/glossary.md?version=v25.3#scheme-object) in the cluster. For example, you could put your company name there, cluster region, etc. * `ydb_database_name`. It will be the second path component for all [scheme objects](https://ydb.tech/docs/en/concepts/glossary.md?version=v25.3#scheme-object) in the database. For example, you could put the use case or project name there. * `default_disk_type`. If you are using [NVMe](https://en.wikipedia.org/wiki/NVM_Express) or rotating [HDD drives](https://en.wikipedia.org/wiki/Hard_disk_drive), change this setting to `NVME` or `ROT`, respectively. * `ydb_config`: * Any YDB settings can be adjusted via this field, see [YDB Cluster Configuration](https://ydb.tech/docs/en/reference/configuration/index.md?version=v25.3) for more details. * YDB playbooks automatically set some YDB settings based on Ansible inventory (like `hosts` or [TLS-related](https://ydb.tech/docs/en/reference/configuration/index.md?version=v25.3) settings), if you configure them explicitly in `ydb_config` it will have a priority. * If you prefer to keep YDB-specific settings separate from the Ansible inventory, replace this whole setting with a string containing file path to a separate [YAML](https://en.wikipedia.org/wiki/YAML) file with YDB configuration. * `ydb_storage_node_cores` and `ydb_database_node_cores`. If your server has more than 16 CPU cores, increase these so they sum up to the actual available number. If you have over 64 cores per server, consider running multiple database nodes per server using `ydb_database_nodes_per_server`. Aim for $ydb\_storage\_node\_cores + ydb\_database\_nodes\_per\_server \times ydb\_database\_node\_cores = available\_cores$. {% cut "Optional settings" %} There are multiple options to specify which exactly YDB executables you want to use for the cluster: * `ydb_version`: automatically download one of the [YDB official releases](https://ydb.tech/docs/en/downloads/index.md?version=v25.3#ydb-server) by version number. For example, `23.4.11`. * `ydb_git_version`: automatically compile the YDB executables from the source code, downloaded from [the official GitHub repository](https://github.com/ydb-platform/ydb). The setting's value is a branch, tag, or commit name. For example, `main`. * `ydb_archive`: a local filesystem path for a YDB distribution archive [downloaded](https://ydb.tech/docs/en/downloads/index.md?version=v25.3#ydb-server) or otherwise prepared in advance. * `ydbd_binary` and `ydb_cli_binary`: local filesystem paths for YDB server and client executables, [downloaded](https://ydb.tech/docs/en/downloads/index.md?version=v25.3#ydb-server) or otherwise prepared in advance. Installing a [connector](https://ydb.tech/docs/en/concepts/query_execution/federated_query/architecture.md?version=v25.3#connectors) may be necessary for using [federated queries](https://ydb.tech/docs/en/concepts/query_execution/federated_query/index.md?version=v25.3). The playbook can deploy the [fq-connector-go](https://ydb.tech/docs/en/devops/deployment-options/manual/federated-queries/connector-deployment.md?version=v25.3#fq-connector-go) to the hosts with dynamic nodes. Use the following settings: * `ydb_install_fq_connector` - set to `true` for installing the connector. * Choose one of the available options for deploying fq-connector-go executables: * `ydb_fq_connector_version`: automatically download one of the [fq-connector-go official releases](https://github.com/ydb-platform/fq-connector-go/releases) by version number. For example, `v0.7.1`. * `ydb_fq_connector_git_version`: automatically compile the fq-connector-go executable from the source code, downloaded from [the official GitHub repository](https://github.com/ydb-platform/fq-connector-go). The setting's value is a branch, tag, or commit name. For example, `main`. * `ydb_fq_connector_archive`: a local filesystem path for a fq-connector-go distribution archive [downloaded](https://github.com/ydb-platform/fq-connector-go/releases) or otherwise prepared in advance. * `ydb_fq_connector_binary`: local filesystem paths for fq-connector-go executable, [downloaded](https://github.com/ydb-platform/fq-connector-go/releases) or otherwise prepared in advance. * `ydb_tls_dir` – specify a local path to a folder with TLS certificates prepared in advance. It must contain the `ca.crt` file and subdirectories with names matching node hostnames, containing certificates for a given node. If omitted, self-signed TLS certificates will be generated automatically for the whole YDB cluster. * `ydb_brokers` – list the FQDNs of the broker nodes. For example: ```yaml ydb_brokers: - static-node-1.ydb-cluster.com - static-node-2.ydb-cluster.com - static-node-3.ydb-cluster.com ``` The optimal value of the `ydb_database_storage_groups` setting in the `vars` section depends on available disk drives. Assuming only one database in the cluster, use the following logic: * For production-grade deployments, use disks with a capacity of over 800 GB and high IOPS, then choose the value for this setting based on the cluster topology: * For `block-4-2`, set `ydb_database_storage_groups` to 95% of your total disk drive count, rounded down. * For `mirror-3-dc`, set `ydb_database_storage_groups` to 84% of your total disk drive count, rounded down. * For testing YDB on small disks, set `ydb_database_storage_groups` to 1 regardless of cluster topology. The values of the `system_timezone` and `system_ntp_servers` variables depend on the infrastructure properties where the YDB cluster is being deployed. By default, `system_ntp_servers` includes a set of NTP servers without considering the geographical location of the infrastructure on which the YDB cluster will be deployed. We strongly recommend using a local NTP server for on-premise infrastructure and the following NTP servers for cloud providers: {% list tabs %} - AWS * `system_timezone`: USA/ * `system_ntp_servers`: [169.254.169.123, time.aws.com] [Learn more](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html#configure-time-sync) about AWS NTP server settings. - Azure * You can read about how time synchronization is configured on Azure virtual machines in [this](https://learn.microsoft.com/en-us/azure/virtual-machines/linux/time-sync) article. - Alibaba * The specifics of connecting to NTP servers in Alibaba are described in [this article](https://www.alibabacloud.com/help/en/ecs/user-guide/alibaba-cloud-ntp-server). - Yandex Cloud * `system_timezone`: Europe/Moscow * `system_ntp_servers`: [0.ru.pool.ntp.org, 1.ru.pool.ntp.org, ntp0.NL.net, ntp2.vniiftri.ru, ntp.ix.ru, ntps1-1.cs.tu-berlin.de] [Learn more](https://yandex.cloud/en/docs/tutorials/infrastructure-management/ntp) about Yandex Cloud NTP server settings. {% endlist %} {% endcut %} ### Changing the root User Password {#change-password} Next, you can set the password for the initial user specified in the `ydb_user` setting (`root` by default). This user will initially have the full access rights in the cluster, but this can be later adjusted if necessary. Create `inventory/99-inventory-vault.yaml` with the following contents (replace `` with the actual password): ```yaml all: children: ydb: vars: ydb_password: ``` Encrypt this file using the command `ansible-vault encrypt inventory/99-inventory-vault.yaml`. It would require you to manually enter the encryption password, which is independent from the `ydb_password` setting value and better be different. Alternatively, you can save the encryption password to a separate file and configure the `vault_password_file` Ansible setting with the file path. See [Ansible Vault documentation](https://docs.ansible.com/ansible/latest/vault_guide/index.html) for more details on how this works. ### Prepare the YDB Configuration File {#ydb-config-prepare} ## Deploying the YDB Cluster After all the preparations explained above are complete, the actual initial cluster deployment is as simple as running the following command from the working directory: ```bash ansible-playbook ydb_platform.ydb.initial_setup ``` Shortly after start, you'll be asked to confirm full wipe of the configured disk drives. Then, it can take tens of minutes to finish deployment depending on the environment and settings. Under the hood, this playbook follows roughly the same steps as explained in instructions for [manual YDB cluster deployment](https://ydb.tech/docs/en/devops/deployment-options/manual/initial-deployment.md?version=v25.3). ### Checking the Cluster State {#cluster-state} On the last step, the playbook will run a few test queries using real temporary tables to double-check if everything is indeed working as intended. On success, you'll see the `ok` status, `failed=0` for each server, and results of these test queries (3 and 6) if the playbook output is set to be verbose enough. {% cut "Example output" %} ```txt ... TASK [ydb_platform.ydb.ydbd_dynamic : run test queries] ******************************************************************************************************************************************************* ok: [static-node-1.ydb-cluster.com] => (item={'instance': 'a'}) => {"ansible_loop_var": "item", "changed": false, "item": {"instance": "a"}, "msg": "all test queries were successful, details: {\"count\":3,\"sum\":6}\n"} ok: [static-node-1.ydb-cluster.com] => (item={'instance': 'b'}) => {"ansible_loop_var": "item", "changed": false, "item": {"instance": "b"}, "msg": "all test queries were successful, details: {\"count\":3,\"sum\":6}\n"} ok: [static-node-2.ydb-cluster.com] => (item={'instance': 'a'}) => {"ansible_loop_var": "item", "changed": false, "item": {"instance": "a"}, "msg": "all test queries were successful, details: {\"count\":3,\"sum\":6}\n"} ok: [static-node-2.ydb-cluster.com] => (item={'instance': 'b'}) => {"ansible_loop_var": "item", "changed": false, "item": {"instance": "b"}, "msg": "all test queries were successful, details: {\"count\":3,\"sum\":6}\n"} ok: [static-node-3.ydb-cluster.com] => (item={'instance': 'a'}) => {"ansible_loop_var": "item", "changed": false, "item": {"instance": "a"}, "msg": "all test queries were successful, details: {\"count\":3,\"sum\":6}\n"} ok: [static-node-3.ydb-cluster.com] => (item={'instance': 'b'}) => {"ansible_loop_var": "item", "changed": false, "item": {"instance": "b"}, "msg": "all test queries were successful, details: {\"count\":3,\"sum\":6}\n"} PLAY RECAP **************************************************************************************************************************************************************************************************** static-node-1.ydb-cluster.com : ok=167 changed=80 unreachable=0 failed=0 skipped=167 rescued=0 ignored=0 static-node-2.ydb-cluster.com : ok=136 changed=69 unreachable=0 failed=0 skipped=113 rescued=0 ignored=0 static-node-3.ydb-cluster.com : ok=136 changed=69 unreachable=0 failed=0 skipped=113 rescued=0 ignored=0 ``` {% endcut %} As a result of executing the `ydb_platform.ydb.initial_setup` playbook, a YDB cluster will be created. It will contain a [domain](https://ydb.tech/docs/en/concepts/glossary.md?version=v25.3#domain) named with the `ydb_domain` setting (`Root` by default), a [database](https://ydb.tech/docs/en/concepts/glossary.md?version=v25.3#database) named with the `ydb_database_name` setting (`database` by default), and an initial [user](https://ydb.tech/docs/en/concepts/glossary.md?version=v25.3#access-user) named with the `ydb_user` setting (`root` by default). ## Optional Next Steps The easiest way to explore the newly deployed cluster is by using [Embedded UI](https://ydb.tech/docs/en/reference/embedded-ui/index.md?version=v25.3) running on port 8765 of each server. In the likely case that you don't have direct access to this port from your browser, you can set up SSH tunneling. For this, execute the command `ssh -L 8765:localhost:8765 -i @` on your local machine (add more options if necessary). After successfully establishing the connection, you can navigate to the [localhost:8765](http://localhost:8765) URL via browser. The browser might ask you to accept a security exception. An example of how it might look like: ![ydb-web-ui](../../../_assets/ydb-web-console.png) After successfully creating the YDB cluster, you can check its state using the following Embedded UI page: [http://localhost:8765/monitoring/cluster/tenants](http://localhost:8765/monitoring/cluster/tenants). It might look like this: ![ydb-cluster-check](../../../_assets/ydb-cluster-check.png) This section displays the following parameters of the YDB cluster, reflecting its state: * `Tablets` – a list of running [tablets](https://ydb.tech/docs/en/concepts/glossary.md?version=v25.3#tablet). All tablet state indicators should be green. * `Nodes` – the number and state of storage and database nodes launched in the cluster. The node state indicator should be green, and the number of created to launched nodes should be equal. For example, 18/18 for a nine-node cluster with a single database node per server. The `Load` indicators (amount of RAM used) and `Storage` (amount of disk space used) should also be green. You can check the state of the storage group in the `storage` section – [http://localhost:8765/monitoring/cluster/storage](http://localhost:8765/monitoring/cluster/storage): ![ydb-storage-gr-check](../../../_assets/ydb-storage-gr-check.png) The `VDisks` indicators should be green, and the `state` status (found in the tooltip when hovering over the Vdisk indicator) should be `Ok`. More about the cluster state indicators and monitoring can be read in the article [YDB Monitoring](https://ydb.tech/docs/en/reference/embedded-ui/ydb-monitoring.md?version=v25.3). ### Cluster Testing {#testing} You can test the cluster using the built-in load tests in YDB CLI. To do this, [install YDB CLI](https://ydb.tech/docs/en/reference/ydb-cli/install.md?version=v25.3) and create a profile with connection parameters, replacing the placeholders: ```shell ydb \ config profile create \ -d // \ -e grpcs://:2135 \ --ca-file $(pwd)/files/TLS/certs/ca.crt \ --user root \ --password-file ``` Command parameters and their values: * `config profile create` – This command is used to create a connection profile. You specify the profile name. More detailed information on how to create and modify profiles can be found in the article [Creating and updating profiles](https://ydb.tech/docs/en/reference/ydb-cli/profile/create.md?version=v25.3). * `-e` – Endpoint, a string in the format `protocol://host:port`. You can specify the FQDN of any cluster node and omit the port. By default, port 2135 is used. * `--ca-file` – Path to the root certificate for connections to the database using `grpcs`. * `--user` – The user for connecting to the database. * `--password-file` – Path to the password file. Omit this to enter the password manually. You can check if the profile has been created using the command `ydb config profile list`, which will display a list of profiles. After creating a profile, you need to activate it with the command `ydb config profile activate `. To verify that the profile has been activated, you can rerun the command `ydb config profile list` – the active profile will have an `(active)` mark. To execute a [YQL](https://ydb.tech/docs/en/yql/reference/index.md?version=v25.3) query, you can use the command `ydb sql -s 'SELECT 1;'`, which will return the result of the `SELECT 1` query in table form to the terminal. After checking the connection, you can create a test table with the command: `ydb workload kv init --init-upserts 1000 --cols 4`. This will create a test table `kv_test` consisting of 4 columns and 1000 rows. You can verify that the `kv_test` table was created and filled with test data by using the command `ydb sql -s 'select * from kv_test limit 10;'`. The terminal will display a table of 10 rows. Now, you can perform cluster performance testing. The article [Key-Value load](https://ydb.tech/docs/en/reference/ydb-cli/workload-kv.md?version=v25.3) describes multiple types of workloads (`upsert`, `insert`, `select`, `read-rows`, `mixed`) and the parameters for their execution. An example of executing the `upsert` test workload with the parameter to print the execution time `--print-timestamp` and standard execution parameters is: `ydb workload kv run upsert --print-timestamp`: ```text Window Txs/Sec Retries Errors p50(ms) p95(ms) p99(ms) pMax(ms) Timestamp 1 727 0 0 11 27 71 116 2024-02-14T12:56:39Z 2 882 0 0 10 21 29 38 2024-02-14T12:56:40Z 3 848 0 0 10 22 30 105 2024-02-14T12:56:41Z 4 901 0 0 9 20 27 42 2024-02-14T12:56:42Z 5 879 0 0 10 22 31 59 2024-02-14T12:56:43Z ... ``` After completing the tests, the `kv_test` table can be deleted with the command: `ydb workload kv clean`. More details on the options for creating a test table and tests can be read in the article [Key-Value load](https://ydb.tech/docs/en/reference/ydb-cli/workload-kv.md?version=v25.3). ## See Also * [Extra Ansible configuration examples](https://github.com/ydb-platform/ydb-ansible-examples) * [Restarting YDB Clusters deployed with Ansible](https://ydb.tech/docs/en/devops/deployment-options/ansible/restart.md?version=v25.3) * [Updating Configuration of YDB Clusters Deployed with Ansible](https://ydb.tech/docs/en/devops/deployment-options/ansible/update-config.md?version=v25.3) * [Updating YDB Version on Clusters Deployed with Ansible](https://ydb.tech/docs/en/devops/deployment-options/ansible/update-executable.md?version=v25.3)