Managing Clusters and Databases
Creating and Configuring a Cluster
Follow these steps to create a database cluster:
- Click Create cluster in the Managed Databases section of the Cloud platform project.
- Fill in the fields in the new form:
- enter the database cluster name;
- select the pool (it will not be possible to change it after creation);
- select the DBMS version (it will not be possible to change it after creation);
- select node configuration;
- add replicas to the cluster if it is necessary to make it fault tolerant;
- select a cluster subnet that has as many addresses as there are servers to add to the cluster;
- configure the connection pooler;
- change the DBMS settings if necessary. Learn more about the settings in the instructions for PostgreSQL and MySQL.
- Click Create a database cluster.
After the cluster status changes to Active, go to the cluster page by clicking on the cluster name.
You can create databases, users, and configure access rights on the cluster page.
The Settings tab contains information required to connect to the cluster.
Network Access Control
By default, all addresses are allowed to connect to the database cluster. You can connect to a cluster in a public subnet from any address if you have a username and password. To a cluster in a private subnet — from the cluster subnet and from those subnets that are connected to the cluster subnet by a router.
You can restrict a list of IP addresses that can be connected to the database cluster. To do this, from the Control panel:
- Go to the Managed Databases section.
- Open the cluster page and go to the Settings tab.
- Click Edit in the Network access control section.
- Enter all IP addresses and subnets that should be allowed access to the cluster. Only IPv4 addressing is supported. Please note that in the list of allowed IP addresses, you must specify all addresses that need access to the cluster. Otherwise, you may lose access to the cluster from its own subnet.
All addresses, except for those listed in the list, will be denied connection.
Please note that when restoring a cluster from backup, the list of IP addresses is not saved. For a new cluster, you need to create it again.
History of Operations
The Operations tab displays the main operations on the cluster, the time they started and finished, and the result with which the operations were completed (done or not). The history of operations will help you track which operations were not completed and at what time certain operations were performed on the cluster, as well as troubleshoot problems. This allows you to track all the operations and diagnose problems.
The history of operations will display the following operations:
- creating clusters;
- creating/deleting databases;
- creating/deleting users;
- assigning access rights/denying access;
- scaling the cluster;
- renaming the cluster.
- ACTIVE – the cluster is available;
- PENDING_CREATE – the cluster is being created;
- PENDING_DELETE – the cluster is deleted;
- DELETED – the cluster is deleted;
- ERROR – an error has occurred, create a ticket;
- PENDING_UPDATE – changes are being applied to the cluster;
- RESIZING – the cluster is being scaled;
- DISK_FULL – the cluster is in read-only mode because the volume is full;
- DEGRADED – some cluster nodes are unavailable.
Managing via Terraform
Learn more about getting started with Terraform.
You can create MySQL and PostgreSQL clusters via Terraform.