CirrusGrid PaaS provides an on-demand automatic clusterization for some of the managed templates. Such automation significantly simplifies and speeds up the creation of a reliable production-ready cluster for your project.
Below, we’ll consider the following points:
- supported stacks (with clusterization specifics)
- auto-clustering management
Templates with Supported Auto-Clustering #
Currently, the following templates support the newly added clustering feature (with even more stacks to be added in the future):
- application servers – GlassFish, Payara, Jenkins, WildFly
- SQL databases – MySQL, MariaDB, PostgreSQL
- NoSQL database – Couchbase, MongoDB
- storage server – Shared Storage Container
GlassFish #
Interconnection of the GlassFish servers with pre-configured session replication and load balancing.
Payara #
Interconnection of the Payara servers with pre-configured session replication and load balancing.
Jenkins #
A master Jenkins node in the master-slave mode with auto-scalable Java Engine workers and pre-installed plugins to support building and deployment automation for organizing continuous integration (CI) and continuous delivery (CD) pipelines.
WildFly #
WildFly nodes in Domain Mode with enabled clustering to get high availability and guarantee the continuous performance of a deployed Java EE application.
MySQL #
Auto-Clustering is provided for the 5.7.x and 8.x MySQL versions only.
Automatic clusterization of the databases with pre-configured replication and auto-discovery of the nodes.
Based on your requirements, you can select Scheme of the following types:
Master-Master with Extra Slaves
Pre-configured replication with two interconnected master databases. During the horizontal scaling, the cluster is extended with additional slave nodes.
Master-Slave with Extra Slaves
Pre-configured replication with one master and one slave database. During the horizontal scaling, the cluster is extended with additional slave nodes.
MariaDB #
Auto-Clustering is provided for the 10.x MariaDB versions only.
Automatic clusterization of the databases with pre-configured replication and auto-discovery of the nodes.
Based on your requirements, you can select Scheme of the following types:
Master-Master with Extra Slaves
Pre-configured replication with two interconnected master databases. During the horizontal scaling, the cluster is extended with additional slave nodes.
Master-Slave with Extra Slaves
Pre-configured replication with one master and one slave database. During the horizontal scaling, the cluster is extended with additional slave nodes.
Galera Cluster
All servers can accept updates even if being issued concurrently.
PostgreSQL #
Pre-configured PostgreSQL database cluster with asynchronous master-slave replication and automatic addition of the new nodes into the cluster (as slaves).
Couchbase #
Automatically interconnected Couchbase servers with the pre-configured auto-scaling and rebalancing to provide a single highly available data storing system.
Shared Storage Container #
Automatically configured, reliable storage cluster (replicated volume) based on the Gluster solution, which ensures data safety. In case of failure of one or several nodes, the AutoFS client automatically switches to the working instances, providing storage high-availability.
Auto-Clustering Management #
1. The Auto-Clustering feature can be enabled for the node group through the same-named switcher in the central part of the topology wizard (if available for the selected stack).
Tip: Based on the specific implementation, the Auto-Clustering option can be:
- mandatory enabled (e.g. for the Couchbase database)
- provided with some additional settings (e.g. cluster scheme and ProxySQL load balancer for the MySQL database)
- restricted by the minimum/maximum nodes count and/or scaling mode (e.g for the MariaDB Galera type)auto-clustering validation
2. Herewith, to get additional information on the cluster to be created, you can hover over the question mark next to the switcher. Within the appropriate pop-up frame, you can find a short description, which is usually supplemented with a topology scheme and a link to the more detailed overview.
Tip: Additional info on the various database cluster types can be viewed by hovering over the appropriate Scheme:
3. The other settings can be configured just as for any regular environment.
Note: After being configured, auto-clustering cannot be disabled from the topology wizard.
4. If needed, you can track the cluster configuration logs via the platform console:
https://app.qloud.asia/console
For example, you can use this info for debugging while developing packaged solutions with Cloud Scripting, which utilize the auto-clustering feature.
