9.1.1. Is ClusterControl free?¶
ClusterControl has a Community Edition that is free forever, available features include deployment and monitoring of clusters/servers. Please see the ClusterControl product page for details on features.
After installation, you will get a 30-day free trial license (no credit card or signing required) with all enterprise features enabled. After the trial license expires, it will default back to community edition.
9.1.2. Is there a live demo site where I can try out ClusterControl?¶
There is no live demo site available at the moment, although we have some webinars that show the product in details. We recommend users to install ClusterControl on a test server/VM and give it a try.
You can also contact Severalnines so we can prepare a demo for you - usually we can do this within 24 to 48 hours after the initial enquiry.
9.1.3. Can I purchase the license for the first year only?¶
Subscriptions are annual, and include software license, all updates and technical support. At the end of the subscription period, you can choose to renew the subscription or continue with the Community Edition. When the license expires, ClusterControl defaults to the Community Edition.
9.1.4. My 30-day demo license has expired but I haven’t had enough time to test ClusterControl. Can I request for extension?¶
Of course. Please use our contact us page or email directly to sales[at]severalnines.com
9.1.5. I would like to subscribe as paid user but have limited budget. What should I do?¶
We’ll be happy to understand your specific requirements. Please contact us at sales[at]severalnines.com.
9.1.6. Can I resell your product?¶
Yes, we have a reseller program. Please email us at sales[at]severalnines.com
9.2.1. Do I need to be a DBA to use ClusterControl?¶
No. We build ClusterControl to be used by DBAs as well as Sysadmins/DevOps to easily manage their databases.
9.2.2. Does ClusterControl run on Windows?¶
No. ClusterControl only runs on RHEL-based and Debian-based with x86_64 architecture.
9.2.3. How do I upgrade ClusterControl?¶
9.2.4. I’m using ClusterControl community version. Which support channel should I use?¶
You can open a thread in our public forum, https://support.severalnines.com/forums. In case you have to share files or logs that might contain sensitive information, please submit a ticket at https://support.severalnines.com/new.
9.2.5. Can I install ClusterControl on RHEL based system but my database cluster is running on Debian?¶
Yes. Starting from 1.2.11, ClusterControl does not depend on the DB nodes’ operating system any longer.
9.2.6. Can I use ClusterControl in an internetless environment?¶
Yes. However some features might not be working well, as explained in Offline Installation page.
9.2.7. Can I have a mix of different SSH users per cluster?¶
It’s possible but not recommended since it will make the deployment more complex. If you choose root as the SSH user, you should use root user for other clusters as well.
9.2.8. Can I use non-privileged SSH user for ClusterControl?¶
Unfortunately, no. ClusterControl requires super-privileged SSH user to perform tasks like deployment, administration and management of the database nodes.
9.2.9. What is difference of MySQL Galera Cluster, Percona XtraDB Cluster and MariaDB Galera Cluster?¶
The Galera technology is developed by Codership Oy and is available as a patch for standard MySQL and InnoDB. Percona and MariaDB leverage the Galera library in Percona XtraDB Cluster (PXC) and MariaDB Galera Cluster respectively.
Since they all leverage the same Galera library, replication performance should be fairly similar. The Codership build usually has the latest version of Galera, although that could change in the future.
9.2.10. I found a bug. Where should I report it?¶
Please report the bug by submiting a support request. For Enterprise customers, bug fixes are provided soonest possible.
9.2.11. My cluster is down. What should I do?¶
Please submit a ticket at https://support.severalnines.com/new. If you are a paying customer, please do this with your company email address so the ticket can be assigned to the appropriate support SLA. Please also include an error report.