New to KubeDB? Please start here.
ClickHouse Horizontal Scaling
This guide will give an overview on how KubeDB Ops-manager operator scales up or down ClickHouse cluster replicas of various component such as Combined, Broker, Controller.
Before You Begin
- You should be familiar with the following
KubeDBconcepts:
How Horizontal Scaling Process Works
The following diagram shows how KubeDB Ops-manager operator scales up or down ClickHouse database components. Open the image in a new tab to see the enlarged version.
The Horizontal scaling process consists of the following steps:
At first, a user creates a
ClickHouseCustom Resource (CR).KubeDBProvisioner operator watches theClickHouseCR.When the operator finds a
ClickHouseCR, it creates required number ofPetSetsand related necessary stuff like secrets, services, etc.Then, in order to scale the various components (ie. ReplicaSet, Shard, ConfigServer etc.) of the
ClickHousecluster, the user creates aClickHouseOpsRequestCR with desired information.KubeDBOps-manager operator watches theClickHouseOpsRequestCR.When it finds a
ClickHouseOpsRequestCR, it halts theClickHouseobject which is referred from theClickHouseOpsRequest. So, theKubeDBProvisioner operator doesn’t perform any operations on theClickHouseobject during the horizontal scaling process.Then the
KubeDBOps-manager operator will scale the related PetSet Pods to reach the expected number of replicas defined in theClickHouseOpsRequestCR.After the successfully scaling the replicas of the related PetSet Pods, the
KubeDBOps-manager operator updates the number of replicas in theClickHouseobject to reflect the updated state.After the successful scaling of the
ClickHousereplicas, theKubeDBOps-manager operator resumes theClickHouseobject so that theKubeDBProvisioner operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on horizontal scaling of ClickHouse cluster using ClickHouseOpsRequest CRD.































