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.
MongoDB Horizontal Scaling
This guide will give an overview on how KubeDB Enterprise operator scales up or down MongoDB database replicas of various component such as ReplicaSet, Shard, ConfigServer, Mongos, etc.
Before You Begin
- You should be familiar with the following
KubeDBconcepts:
How Horizontal Scaling Process Works
The following diagram shows how KubeDB Enterprise operator scales up or down MongoDB 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
MongoDBCustom Resource (CR).KubeDBCommunity operator watches theMongoDBCR.When the operator finds a
MongoDBCR, it creates required number ofStatefulSetsand related necessary stuff like secrets, services, etc.Then, in order to scale the various components (ie. ReplicaSet, Shard, ConfigServer, Mongos, etc.) of the
MongoDBdatabase the user creates aMongoDBOpsRequestCR with desired information.KubeDBEnterprise operator watches theMongoDBOpsRequestCR.When it finds a
MongoDBOpsRequestCR, it halts theMongoDBobject which is referred from theMongoDBOpsRequest. So, theKubeDBCommunity operator doesn’t perform any operations on theMongoDBobject during the horizontal scaling process.Then the
KubeDBEnterprise operator will scale the related StatefulSet Pods to reach the expected number of replicas defined in theMongoDBOpsRequestCR.After the successfully scaling the replicas of the related StatefulSet Pods, the
KubeDBEnterprise operator updates the number of replicas in theMongoDBobject to reflect the updated state.After the successful scaling of the
MongoDBreplicas, theKubeDBEnterprise operator resumes theMongoDBobject so that theKubeDBCommunity operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on horizontal scaling of MongoDB database using MongoDBOpsRequest CRD.






























