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.
Druid Horizontal Scaling
This guide will give an overview on how KubeDB Ops-manager operator scales up or down Druid cluster replicas of various component such as Coordinators, Overlords, Historicals, MiddleManager, Brokers and Routers.
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 Druid 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
DruidCustom Resource (CR).KubeDBProvisioner operator watches theDruidCR.When the operator finds a
DruidCR, it creates required number ofPetSetsand related necessary stuff like secrets, services, etc.Then, in order to scale the various components (i.e. Coordinators, Overlords, Historicals, MiddleManagers, Brokers, Routers) of the
Druidcluster, the user creates aDruidOpsRequestCR with desired information.KubeDBOps-manager operator watches theDruidOpsRequestCR.When it finds a
DruidOpsRequestCR, it halts theDruidobject which is referred from theDruidOpsRequest. So, theKubeDBProvisioner operator doesn’t perform any operations on theDruidobject 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 theDruidOpsRequestCR.After the successfully scaling the replicas of the related PetSet Pods, the
KubeDBOps-manager operator updates the number of replicas in theDruidobject to reflect the updated state.After the successful scaling of the
Druidreplicas, theKubeDBOps-manager operator resumes theDruidobject 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 Druid cluster using DruidOpsRequest CRD.






























