ClusterControl 是您唯一需要部署,監視,自動化和管理開源資料庫的管理系統。它提供了社區版提供的所有功能以及當今市場上最全面的資料庫管理功能。
資料庫自動化
ClusterControl的核心是自動化功能,使您可以自動化必須定期執行的許多資料庫任務,例如部署新集群,添加和擴展新節點,運行備份和升級等等。
企業級
當您的應用程式是24x7全天候且正常運行時間是至關重要的任務時,ClusterControl是您可以依靠的企業級解決方案,其穩定性和性能僅需其他提供商的一小部分成本。
經過實戰測試
ClusterControl確保您的團隊可以輕鬆,安全地部署使用經過實戰檢驗,久經考驗的方法構建的可投入生產的開源資料庫堆棧。
備份與管理
ClusterControl全面的備份管理為本地和雲端環境中的開源資料庫提供持續的數據保護。
監控和警報
ClusterControl提供了跨多個數據中心的所有資料庫部署的統一視圖,使您可以看到全局或深入到各個節點。
部署和擴展
通過ClusterControl的點擊界面,您可以安全地自動執行資料庫設置的部署和擴展,以在短時間內啟動生產就緒環境。
資料庫升級和補丁
ClusterControl可確保您的資料庫保持最新和合規性,並通過使用久經考驗的過程來幫助您應用資料庫升級和補丁程式,從而減少了維護時間。
資料庫安全與合規
ClusterControl確保您的開源資料庫部署始終遵循每種技術的安全模型設置,並通過啟用靜態數據和傳輸中數據的加密來確保關鍵數據的安全。
資料庫運營報告
ClusterControl為您提供有關資料庫操作的運行狀況和穩定性的全面的資料庫操作報告。
數據庫配置管理
通過ClusterControl GUI,可以輕鬆查看當前的資料庫配置並輕鬆進行更改。對於資料庫部署,ClusterControl使用具有合理默認值的預定義資料庫配置模板。
自動資料庫恢復和修復
ClusterControl中的高級自動故障轉移技術可確保您的關鍵任務應用程式在零停機時間內實現高可用性。
提高資料庫性能
ClusterControl提供了部署負載平衡器的功能,並具有高級監視和報告功能,可讓您輕鬆地密切關注資料庫設置的性能。
在雲端中部署,管理和備份資料庫
通過ClusterControl,您可以將高可用性資料庫集群部署並運行到AWS,Microsoft Azure或Google Cloud。借助ClusterControl,您可以壓縮和加密備份,並作為災難恢復計劃的一部分上傳到雲端存儲,所有這些操作都從一個管理界面進行。
Free Community
For deployment and monitoring
- Deployment and monitoring
- Performance advisors
- Community support
Advanced
For production deployments
- Scaling and failover
- Deploy load balancers
- Business hours support
Enterprise
For enterprise-grade deployments
- Enhanced security features
- Reports (health, capacity, etc.)
- 24×7 support
COMMUNITY | ADVANCED | ENTERPRISE | |
ClusterControl Features | Free Forever | Pricing available on request | |
Deployment | |||
Standalone | YES | YES | YES |
Cluster/Replication | YES | YES | YES |
Load Balancers | NO | YES | YES |
Create Local Repositories | NO | YES | YES |
Monitoring | |||
Custom Dashboards | NO | YES | YES |
Fault Detection | NO | YES | YES |
Query Monitor | YES | YES | YES |
Performance Advisors | YES | YES | YES |
Alarms and Notifications | NO | YES | YES |
Management | |||
Operations Center | NO | NO | YES |
Configuration Management | NO | YES | YES |
Backup and Restore | NO | YES | YES |
Backup Verification | NO | NO | YES |
Database Patch Upgrades | NO | YES | YES |
Database User Management | NO | YES | YES |
Develop Custom Advisors | YES | YES | YES |
Node and Cluster Recovery | NO | YES | YES |
Cloud Integration | NO | YES | YES |
Ops Reports | NO | NO | YES |
ProxySQL Management | NO | YES | YES |
Security | |||
Key Management | NO | NO | YES |
Role-based access control | NO | NO | YES |
LDAP / Active Directory authentication | NO | NO | YES |
Backup encryption | NO | NO | YES |
Audit logs | |||
TLS encryption | NO | NO | YES |
Scaling | |||
Add / remove nodes | NO | YES | YES |
Read replicas | NO | YES | YES |
Cluster-to-cluster replication | NO | NO | YES |
Cloning (Galera) | NO | NO | YES |
Support | |||
Number of incidents p/year | 0 | 12 | Unlimited |
Support access | NO | Web/email | Web/email/phone |
Support hours | NO | Business hours | 24 x 7 |
Response time | NO | 1 business day | 2 hours |
Remote login | NO | NO | YES |
Custom builds | NO | NO | YES |
Hardware
Following is the minimal system requirement for the ClusterControl host:
- Architecture: x86_64 only
- RAM: >2 GB
- CPU: >2 cores
- Disk space: >40 GB
- Tested cloud platform:
- AWS EC2
- Google Cloud
- Microsoft Azure
- Digital Ocean
- Internet connection (for selected cluster deployment)
The above should be able to handle a three-node database cluster smoothly.
Capacity Planning
In regards to capacity planning, to simply put into perspective, we have seen real-world use-case where a single ClusterControl server in production with 24 CPUs, 32GB RAM, 150 GB disk space (currently 92% usage) to manage 67 clusters with around 130 nodes (database + load balancers).
CPU
The CPU capacity of the ClusterControl server plays a crucial role in handling various tasks such as monitoring, managing, and orchestrating database clusters. To accommodate a significant workload and ensure scalability for future growth, we recommend a minimum of 8 to 24 CPU cores with multi-threading capabilities.
RAM
Memory availability directly impacts the performance and responsiveness of ClusterControl, especially when handling a large number of database clusters and nodes. For optimal operation, we recommend 8 to 32 GB of RAM. However, considering the increasing complexity of database environments and potential future expansions, provisioning additional memory is advisable. During the installation stage, the installer script tunes the necessary parameters for MySQL and Apache according to the amount of RAM in the host. If you have increased the RAM after the installation, it is recommended to revisit the tuning by looking at this blog post, How to Optimize Performance of ClusterControl and Its Components.
Disk Space
Disk space requirements primarily depend on the size of the monitoring data, logs, backups, and other associated files generated by ClusterControl. Given the example use-case disk utilization of 92% for 150GB, it is recommended to allocate at least 300GB of disk space for the ClusterControl server. This ensures sufficient headroom for data growth and temporary storage needs. If you use ClusterControl as the centralized backup repository, consider adding more disk space, adding another disk or mounting a networked file system like NFS, SMB or iSCSI to cater to this.
Network Bandwidth
ClusterControl relies on network communication for monitoring, provisioning, and managing database clusters. Therefore, it’s essential to ensure adequate network bandwidth to support the expected workload. A Gigabit Ethernet connection or higher is recommended for optimal performance. For inter-WAN communication, consider placing the ClusterControl server at the nearest of the most critical segment (production/primary).
Additional Considerations
High Availability
For mission-critical environments, implementing high availability (HA) for the ClusterControl server is highly recommended. This involves deploying redundant ClusterControl nodes in an active-passive or active-active configuration to ensure continuous operation and fault tolerance. See Standby ClusterControl Server for High Availability or High Availability ClusterControl (CMON HA). Note that CMON HA is only available in the Enterprise edition.
Storage Performance
While sufficient disk space is essential, equally important is the performance of the storage subsystem. Utilizing fast and reliable storage technologies such as solid-state drives (SSDs) or high-performance RAID arrays can significantly improve the responsiveness of ClusterControl, especially during data-intensive operations like backups, restores, scaling and reporting.
Monitoring and Maintenance
Regular monitoring of hardware resources, including CPU, RAM, disk space, and network utilization, is essential to identify potential bottlenecks or capacity issues proactively. Additionally, periodic maintenance tasks such as disk cleanup, log rotation, and performance tuning should be scheduled to optimize the ClusterControl server’s performance and stability.
Operating System
ClusterControl has been tested on the following operating systems:
- Red Hat Enterprise Linux 7.x/8.x/9.x
- CentOS 7.x
- Rocky Linux 8.x/9.x
- AlmaLinux 8.x/9.x
- Ubuntu 18.04/20.04/22.04 LTS
- Debian 10.x/11.x/12.x
- openSUSE Leap 15.3/15.4
- SUSE Linux Enterprise Server 15 SP3/15 SP4
For the monitored nodes, some database systems are limited to a number of operating systems, as shown below:
Database systems | Supported operating system |
|
|
|
|
|
|
|
|
Note
Starting 1.9.5, ClusterControl supports OpenSUSE 15 and SUSE Linux Enterprise Server 15 on selected database systems.
PostgreSQL no longer supports Ubuntu 18.04.
Redis does not support Debian 10.
Software Dependencies
The following softwares are required by ClusterControl:
- MySQL server (5.1 or later, preferably 5.5 or later. MySQL 8.0 is supported only with default_authentication_plugin = mysql_native_password)
- MariaDB server (10.0 or later)
- MySQL client
- Apache webserver (2.4 or later)
- mod_rewrite
- mod_ssl
- Allow .htaccess override
- PHP (5.5 or later, recommended 7.0 or later)
- RHEL/CentOS: php, php-mysql or php-mysqlnd, php-gd, php-ldap, php-curl, php-json, php-xml
- Debian/Ubuntu: php-common, php-mysql or php-mysqlnd, php-gd, php-ldap, php-curl, php-json, php-xml
- Linux Kernel Security (SElinux or AppArmor) – must be disabled or set to permissive mode
- OpenSSH server/client
- BASH (recommended: version 4 or later)
- NTP server – All servers’ time must be synced under one time zone
- socat or netcat – for streaming backups
Note If ClusterControl is installed via installation script (install-cc) or package manager (yum/apt), all dependencies will be automatically satisfied.
Supported Browsers
We highly recommend users to use the following web browsers when accessing ClusterControl UI:
- Google Chrome
- Mozilla Firefox
Ensure to keep up-to-date of these browsers as we are very likely taking advantage of the new features available in the latest version.
Note ClusterControl is built and tested only on the mentioned web browsers. Some major web browsers like Safari, Opera and Microsoft Edge could also work.
Supported Databases
The following table shows supported database clusters with recommended minimum nodes:
Database type | Cluster type | Version | Minimum recommended nodes |
MySQL/MariaDB | MySQL Cluster (NDB) | 7.6[1], 8.0[1] | 5 hosts (2 data nodes + 2 SQL with management nodes + 1 ClusterControl node) |
MySQL/MariaDB replication | 5.6[2], 5.7, 8.0 (MySQL/Percona) 10.3, 10.4, 10.5, 10.6, 10.8, 10.9, 10.10, 10.11 (MariaDB) |
3 hosts (1 primary node + 1 standby primary/replica + 1 ClusterControl node) |
|
Percona XtraDB Cluster MariaDB Galera Cluster |
5.6[2], 5.7, 8.0 (Percona) 10.3, 10.4, 10.5, 10.6, 10.8, 10.9, 10.10, 10.11 (MariaDB) |
4 hosts (3 Galera nodes + 1 ClusterControl node) |
|
Standalone | 5.6[2], 5.7, 8.0 (MySQL/Percona) 10.3, 10.4, 10.5, 10.6, 10.8, 10.9, 10.10, 10.11 (MariaDB) |
2 hosts (1 database node + 1 ClusterControl node) |
|
MongoDB/Percona Server for MongoDB | Sharded cluster | 4.2[2], 4.4, 5.0, 6.0 | 8 hosts (3 config servers / 3 shard servers / 1 mongos + 1 ClusterControl node) |
Replica set | 4 hosts (3 replica servers + 1 ClusterControl node) |
||
PostgreSQL | Standalone | 11, 12, 13, 14, 15 | 2 hosts (1 PostgreSQL node + 1 ClusterControl node) |
Streaming replication | 3 hosts (1 primary node + 1 replica node + 1 ClusterControl node) |
||
TimeScaleDB | Standalone | 11, 12, 13, 14, 15 | 2 hosts (1 TimescaleDB node + 1 ClusterControl node) |
Streaming replication | 3 hosts (1 primary node + 1 replica node + 1 ClusterControl node) |
||
Redis[3] | Replication with Sentinel | 6.x, 7.x | 4 hosts (1 primary node with Sentinel + 2 replica nodes with Sentinel + 1 ClusterControl node) |
Microsoft SQL Server[3] | Standalone | 2019 (15.x), 2022 (16.x) | 2 hosts (1 MSSQL node + 1 ClusterControl node) |
Always On availability groups | 3 hosts (1 primary node + 1 replica node + 1 ClusterControl node) |
||
Elasticsearch[3] | Single-node cluster | 7.17, 8.1, 8.3 | 2 hosts (1 primary and data node + 1 ClusterControl node) |
High availability cluster | 6 hosts (3 primary nodes + 2 data nodes + 1 ClusterControl node) |
[1] Only available via ClusterControl GUI (v1).
[2] Import existing clusters only, not supported for new cluster deployment.
[3] Only available via ClusterControl GUI v2.