Skip to main content

MongoDB- Replication

  • Replication is the process of synchronizing data across multiple servers.
  • Provides redundancy and increases data availability with multiple copies of data of different database servers.
  • It is protects a database from the loss of a single server and recover from hardware failure and service interruptions.
  • 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.
Why we need to use Replication:
1-It is a process to keep your data safe ,
2-high availability of data,
3-disaster recovery ,
3-no down time for maintenance ,
4-read scaling and it is  a transparent to the application.

How replication works in MongoDB

A replica set is a group of MongoDB instances that host the same data set. There is two node first is primary node that receives all write operations and secondary, apply operations from the primary so that they have the same data set. Replica set can have only one primary node.
1. Replica set is the group of nodes generally minimum three nodes are required, one node is primary node and remaining nodes are secondary.
2. At the time of automatic failover or maintenance, election establishes for primary and a new primary node is elected.
3 .After the recovery of failed node, it again join the replica set and works as a secondary node.

A typical diagram of mongodb replication is shown in which client application always interact with primary node and primary node then replicate the data to the secondary nodes.

Replica set features


A cluster of N nodes
Anyone node can be primary
All write operations goes to primary
Automatic failover
Automatic Recovery
Consensus election of primary

Set up a replica set 

In this codefari we will convert standalone mongodb instance to a replica set. To convert to replica set follow the below given steps:
·         Shutdown already running mongodb server.
Now start the mongodb server by specifying --replSet option. Basic syntax of --replSet is given below:


mongod --port "PORT" --dbpath "YOUR_DB_DATA_PATH" --replSet "REPLICA_SET_INSTANCE_NAME"


 Example:


mongod --port 27017 --dbpath "D:\set up\mongodb\data" --replSet rs0


It will start a mongod instance with the name rs0, on port 27017. Now start the command prompt and connect to this mongod instance. In mongo client issue the command rs.initiate() to initiate a new replica set. To check the replica set configuration issue the command rs.conf(). To check the status of replica sete issue the command rs.status().

Add members to replica set


To add members to replica set, start mongod instances on multiple machines. Now start a mongo client and issue a command rs.add().

Syntax:


Basic syntax of rs.add() command is as follows:


>rs.add(HOST_NAME:PORT)

Example:


Suppose your mongod instance name is mongod1.net and it is running on port 27017. To add this instance to replica set issue the command rs.add() in mongo client.


>rs.add("mongod1.net:27017")
> 



You can add mongod instance to replica set only when you are connected to primary node. To check whether you are connected to primary or not issue the command db.isMaster() in mongo client.

Popular posts from this blog

Query to find stored procedures by nested stored procedure name

Problem: Suppose we have a stored procedure which has been used in several stored procedure, I mean stored procedure usp_proc1 is nested in many stored procedures like below
BEGIN DECLARE@ResultTABLE ( IDINT, NAMEVARCHAR(50), [ADDRESS]VARCHAR(255) ) INSERTINTO@Result EXECusp_proc1@Name='codefari' END
So I want to find all those queries who containing usp_proc1
Solution: There is a lot of solutions, I'm giving some of them below. If you want to get the only name of the stored procedures then use the following query. Using join query on system tables syscomments and sysobjects we can get the stored procedures name which containing the particular table, nested procs or any other string.
SELECTDISTINCTo.name FROMsyscommentss INNERJOINsysobjectsoONs.id=o.id

Check for changes to an SQL Server table?

Problem: Suppose your team is working on the under-development project so it might be possible continuous work on the database and perform changes in Table, Stored procedure as per requirement, and daily you have to update the testing server database as per changes are done in developing server database then how it is possible to trace those changes. There are a lot of solutions for this problem which is listed below Solution 1: For SQL Server 2000, 2005 and above use the CHECKSUM command SELECTCHECKSUM_AGG(BINARY_CHECKSUM(*))FROMYour_Table_NameWITH (NOLOCK); That will return the same number each time its run as long as the table contents haven't changed. Unfortunately CHECKSUM does not work always properly to detect changes. It is only a primitive checksum and no CRC calculation. Therefore you can't use it to detect all changes, e. g. symmetrical changes result in the same CHECKSUM! Solution 2: 1.Run the following query. Before executing query replace DB_Name with your database name…

Merge and Merge join transformation in SSIS

MERGE TRANSFORMATION
Using Merge Transformation we can combine two sorted data-set into single data-set basically Merge Transformation used to combines rows from two sorted data flows into one sorted data flow. Following tasks you may perform using Merge Transformation: 1.Suppose we have a scenario like, we need to merge data from a database table and excel means we want to merge data from two different data sources. For such type of scenario, you can use Merge Transformation. 2.If we want to merge data from two same structured tables but exists two different servers. 3.Sometimes we get an error due to data in a row, after correcting errors in the data we can re-merge rows easily. See below explanations may help you to understand Merge Transformation: I do evaluate here, you already know about the data source, data conversion, data flow, task flow, control flow etc. Note:Before Merge transformation, we need to sort the data using Sort Transformation. After sorting data add data path to Merge…