You are looking at the documentation of a prior release. To read the documentation of the latest release, please visit here.

New to KubeDB? Please start here.

MariaDB Horizontal Scaling

This guide will give an overview on how KubeDB Ops Manager scales up or down MariaDB Cluster.

Before You Begin

How Horizontal Scaling Process Works

The following diagram shows how KubeDB Ops Manager scales up or down MariaDB database components. Open the image in a new tab to see the enlarged version.

  Horizontal scaling process of MariaDB
Fig: Horizontal scaling process of MariaDB

The Horizontal scaling process consists of the following steps:

  1. At first, a user creates a MariaDB Custom Resource (CR).

  2. KubeDB Community operator watches the MariaDB CR.

  3. When the operator finds a MariaDB CR, it creates required number of StatefulSets and related necessary stuff like secrets, services, etc.

  4. Then, in order to scale the MariaDB database the user creates a MariaDBOpsRequest CR with desired information.

  5. KubeDB Enterprise operator watches the MariaDBOpsRequest CR.

  6. When it finds a MariaDBOpsRequest CR, it pauses the MariaDB object which is referred from the MariaDBOpsRequest. So, the KubeDB Community operator doesn’t perform any operations on the MariaDB object during the horizontal scaling process.

  7. Then the KubeDB Enterprise operator will scale the related StatefulSet Pods to reach the expected number of replicas defined in the MariaDBOpsRequest CR.

  8. After the successfully scaling the replicas of the StatefulSet Pods, the KubeDB Enterprise operator updates the number of replicas in the MariaDB object to reflect the updated state.

  9. After the successful scaling of the MariaDB replicas, the KubeDB Enterprise operator resumes the MariaDB object so that the KubeDB Community operator resumes its usual operations.

In the next docs, we are going to show a step by step guide on horizontal scaling of MariaDB database using MariaDBOpsRequest CRD.