Limited support This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments. Click here to view the documentation for the current version.

Deploying MongoDB as a replica set

MongoDB is included with and used by BMC Digital Workplace and Remedy with Smart IT (Smart IT). MongoDB is a NoSQL database intended for social data.

Note

The installer for BMC Digital Workplace and Smart IT can install MongoDB only on the same server as it installs BMC Digital Workplace and Smart IT. While that configuration is suitable for development and testing, it does not provide the high availability and scalability that you need for your production environments.

The benefits of MongoDB are the following features:

  • High-performance database: Doesn't use joins or embedding, which make reading and writing data fast.
  • Scalable: Scalable through automatic sharding, which means automatic partitioning of data across partitions.  
  • High availability: MongoDB can be used in high availability environments through replicated servers with automatic fail-over.

MongoDB can be used in high availability environments through replicated servers with automatic fail-over. The benefits of a replica set are the following features:

  • Redundancy: Replication provides redundancy and increases data availability.
  • Recovery: Replication also allows you to recover from hardware failure and service interruptions. With additional copies of the data, you can dedicate one to disaster recovery, reporting, or backup.
  • Read capacity: You can use replication to increase read capacity. Clients have the ability to send read and write operations to different servers.
  • Availability: To increase the locality and availability of data for a distributed environment, you can maintain replica servers in different data centers.

This section includes the following topics:

Related topics

 Upgrading-MongoDB

Knowledge article: MongoDB Support for Smart IT & MyIT FAQ

Additional resources

Deployment model


Best practice
BMC recommends that you deploy a minimum of 3 node (always have odd number of servers)  MongoDB replica-set – one primary and two secondary servers. 

The following diagram illustrates the deployment model for MongoDB.

MongoDB_deployment_model.png

If your deployment includes multiple data centers for redundancy, your single replica set spans multiple data centers. For example, you might have a replica set with 5 nodes spanning 3 data centers: two members to Data Center 1, two members to Data Center 2, and one member to Data Center 3. If any data center goes down, the replica set remains writable, as the remaining members can hold an election.

Types of servers

Primary server

Secondary server

  • Stores the data.
  • All read/write operations go to this server from any client.
  • Stores backup data and is synchronized with the primary server.  
  • If the primary server is unavailable, the replica set elects a secondary server to become the primary server.

Deployment process

The following table summarizes the process of deploying MongoDB securely in a production environment:


Where to go from here

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*