We use cookies and other similar technology to collect data to improve your experience on our site, as described in our Privacy Policy.

AppsCode
  • KubeDB

    Run Production-Grade Databases on Kubernetes

    arrow_forward
    Stash

    Backup and Recovery Solution for Kubernetes

    arrow_forward
    KubeVault

    Run Production-Grade Vault on Kubernetes

    arrow_forward
    Voyager

    Secure HAProxy Ingress Controller for Kubernetes

    arrow_forward
    ConfigSyncer

    Kubernetes Configuration Syncer

    arrow_forward
    Guard

    Kubernetes Authentication WebHook Server

    arrow_forward
    KubeDB

    KubeDB simplifies Provision, Upgrade, Scaling, Volume Expansion, Monitor, Backup, Restore for various Databases in Kubernetes on any Public & Private Cloud

    • task_altLower administrative burden
    • task_altNative Kubernetes Support
    • task_altPerformance
    • task_altAvailability and durability
    • task_altManageability
    • task_altCost-effectiveness
    • task_altSecurity
    Stash

    A complete Kubernetes native disaster recovery solution for backup and restore your volumes and databases in Kubernetes on any public and private clouds.

    • task_altDeclarative API
    • task_altBackup Kubernetes Volumes
    • task_altBackup Database
    • task_altMultiple Storage Support
    • task_altDeduplication
    • task_altData Encryption
    • task_altVolume Snapshot
    • task_altPolicy Based Backup
    KubeVault

    KubeVault is a Git-Ops ready, production-grade solution for deploying and configuring Hashicorp's Vault on Kubernetes.

    • task_altVault Kubernetes Deployment
    • task_altAuto Initialization & Unsealing
    • task_altVault Backup & Restore
    • task_altConsume KubeVault Secrets with CSI
    • task_altManage DB Users Privileges
    • task_altStorage Backend
    • task_altAuthentication Method
    • task_altDatabase Secret Engine
    Voyager

    Secure HAProxy Ingress Controller for Kubernetes

    • task_altHTTP & TCP
    • task_altSSL
    • task_altPlatform support
    • task_altHAProxy
    • task_altPrometheus
    • task_altLet's Encrypt
    configsyncer

    Kubernetes Configuration Syncer

    • task_altConfiguration Syncer
    Guard

    Kubernetes Authentication WebHook Server

    • task_altIdentity Providers
    • task_altCLI
    • task_altRBAC
  • RESOURCES
  • Webinar New
CONTACT SALES
KubeDB KubeDB
github-icon twitterx-icon
TRY NOW FREE
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

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.

  Horizontal scaling process of MongoDB
Fig: Horizontal scaling process of MongoDB

The Horizontal scaling process consists of the following steps:

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

  2. KubeDB Community operator watches the MongoDB CR.

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

  4. Then, in order to scale the various components (ie. ReplicaSet, Shard, ConfigServer, Mongos, etc.) of the MongoDB database the user creates a MongoDBOpsRequest CR with desired information.

  5. KubeDB Enterprise operator watches the MongoDBOpsRequest CR.

  6. When it finds a MongoDBOpsRequest CR, it halts the MongoDB object which is referred from the MongoDBOpsRequest. So, the KubeDB Community operator doesn’t perform any operations on the MongoDB 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 MongoDBOpsRequest CR.

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

  9. After the successful scaling of the MongoDB replicas, the KubeDB Enterprise operator resumes the MongoDB 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 MongoDB database using MongoDBOpsRequest CRD.

What's on this Page

Search
Improve This Page