Unsupported content

 

This version of the documentation is no longer supported. 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

The following topics are provided

Purpose of MongoDB

MongoDB is included with and used by BMC MyIT and BMC Remedy with Smart IT (Smart IT). MongoDB is a database intended for very large amounts of data.

The installer for BMC MyIT and SmartIT can install MongoDB only on the same server as it installs BMC MyIT 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.

Benefits

  • 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.

Purpose of a replica set

MongoDB can be used in high availability environments through replicated servers with automatic fail-over.

Benefits

  • RedundancyReplication 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.

Deployment model

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. 
While increasing the number of mongodb nodes add a arbiter when you have even number of mongodb replica nodes.

The following diagram illustrates the deployment model for MongoDB

Types of servers

Primary serverSecondary serverArbiter 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.
  • Stores no data,
  • Cannot become the primary server during failover, and participates in the election process during failover only.
  • Typically, arbiters are required only to break ties when there is an even number of secondary servers.

Database search

BMC Remedy with Smart IT (Smart IT) and BMC MyIT uses the built-in search of MongoDB. However, with MongoDB 3.0.xx, WiredTiger engine is available which has considerably improved the performance. Thus, for search you now have the following options:

  • Full Text SearchBMC recommends that you use Full Text Search which is available by default.
  • Elasticsearch: With this release, version 1.4.2 is supported. See, Configure Elasticsearch with MongoDB.

You must configure search after you have completed the installation of SmartIT and BMC MyIT. 

Deployment process

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

StepActionDescription
1Review the supported versions

MongoDB supported version

  • MongoDB 2.6.x
  • Provided version: MongoDB 3.0.6

Elasticsearch supported version

  • (MongoDB 3.0.xx) Elasticsearch 1.4.2
2

Install MongoDB

You must install Mongo DB on the primary, secondary, and arbiter servers.
3Configure MongoDB as a replica setYou must perform these steps only on the primary server
4Apply security settings

You must perform these settings only for bundled Mongo DB. For replicated DB security settings are taken care of during the installation of Mongo DB.

BMC recommends that you apply security settings using the authentication method.

At this stage you must store the MongoDB password in encrypted format in the configuration file.

5

Configure search

For search you now have the following options:

    • Full Text Search: BMC recommends that you use Full Text Search which is available by default. 
    • Elasticsearch: With this release, version 1.4.2 is supported. See, Configure Elasticsearch with MongoDB.

Related topics

Upgrading MongoDB

Additional resources

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Peter Romain

    The version of MongoDB is 3.0.6 when using the packaged version in the MyIT installer

    Nov 13, 2015 04:26
    1. Hemant Baliwala

      Thanks Peter. 

      I have updated the topic. 

      Regards, 

      Hemant

      Nov 19, 2015 01:42
  2. Thomas Hammer

    Under "MongoDB supported version" only 3.0.6 is listed, not 3.x, not 3.0.x

    For Elastic search 1.4.2 (which we don't need anymore with MongoDB 3.x) also 3.0.xx is mentioned. According to my interpretation this will also include 3.0.8.

    As it seems the most current versions of MongoDB are not supported in general, for 3.0.8 or the 3.2.x versions are not listed.

    Are we forced to choose 3.0.6 from the MongoDB download section, despite of bug fixes in newer versions? Is 3.0.8 only supported when using Elastic search?

     

    Please clarify. Thank you.

     

    P:S: On the following page it seems to be correct and consistent.

    https://docs.bmc.com/docs/display/public/myit30/Compatibility+matrix

    Jan 08, 2016 04:27