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
KubeDB
concepts:
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
MongoDB
Custom Resource (CR).KubeDB
Community operator watches theMongoDB
CR.When the operator finds a
MongoDB
CR, it creates required number ofStatefulSets
and related necessary stuff like secrets, services, etc.Then, in order to scale the various components (ie. ReplicaSet, Shard, ConfigServer, Mongos, etc.) of the
MongoDB
database the user creates aMongoDBOpsRequest
CR with desired information.KubeDB
Enterprise operator watches theMongoDBOpsRequest
CR.When it finds a
MongoDBOpsRequest
CR, it halts theMongoDB
object which is referred from theMongoDBOpsRequest
. So, theKubeDB
Community operator doesn’t perform any operations on theMongoDB
object during the horizontal scaling process.Then the
KubeDB
Enterprise operator will scale the related StatefulSet Pods to reach the expected number of replicas defined in theMongoDBOpsRequest
CR.After the successfully scaling the replicas of the related StatefulSet Pods, the
KubeDB
Enterprise operator updates the number of replicas in theMongoDB
object to reflect the updated state.After the successful scaling of the
MongoDB
replicas, theKubeDB
Enterprise operator resumes theMongoDB
object so that theKubeDB
Community 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.