Question

How to setup MongoDB replica set with Business Intelligence (BI) connector on AWS Cloud environment. I already have MongoDB replica set on AWS Cloud environment. I am trying to generate reports out of the MongoDB data from AWS.

Answer 1

MongoDB Replica Set -> First of all we should known about MongoDB Replica Set

We can achieve high availability and failover with the help of Replica Sets in MongoDB. In this configuration application/client can read and write data from/to primary node. The changes in primary node are replicated to secondary node using oplog (operations log). The secondary node can be used for read only operations depending on the use case. The main advantage of replica set is that it offers automatic failover mechanism in case primary node goes down.

MongoDB BI Connector

Version: 2019.2 Applies to: Tableau Desktop, Tableau Prep

This article describes how to connect Tableau to MongoDB Business Intelligence (BI) data and set up the data source.

Before you begin

Before you begin, gather this connection information:

• Name of the server that hosts the database you want to connect to

• User name and password, if MongoDB authentication is enabled

• Database name associated with the user's credentials, if MongoDB authentication is enabled

• Are we connecting to an SSL server?

• (Optional) Initial SQL statement to run every time Tableau connects

You must install and run the MongoDB Connector for BI, version 2.1 or later, before you can connect Tableau to your MongoDB BI data.

Driver required

Make the connection and set up the data source

Replica Set Components:

1. Primary Members: By default, all read, write transactions are made on the primary node
2. Secondary Members: Any changes made on primary nodes are replicated to secondary nodes using oplogs.
3. Arbitar Members: An arbitar is an optional member of the replica set that does not take part in replication. It only takes part in the selection process of new primary.
4. Selection Process: In case a primary node goes down, the automatic selection process takes place between remaining secondary nodes. And if number of secondary nodes are even, arbitar member acts as a tie-broker to ensure decision is reached.

reachaad To emsune de esian cliat lApplicaton Peards Peels Peaoi apel unte Sendarg Peplica t Remany Pe plicaset 5 endany Peplicaset

1. Setup Replica Sets on Single EC2 Instance

For setting up test environment in few clicks, I am using AWS EC2 (Amazon Linux) for demonstration purpose. You can download Mongo package from MongoDB official website. Once you have MongoDB downloaded, you need to create a data folder for each mongo instances. I’m on a Amazon Linux (t2.micro) and created mongo-data0, mongo-data1 and mongo-data2.

2. Access Replica Sets
If you want you can add each node to have a separate name, to do so you can add the following entry to /etc/hosts:
127.0.0.1 mongo1 mongo2 mongo3
Once done you are ready to connect to Mongo DB Replica Set. You can start accessing replica set by using the command below in your terminal

1 2 3 4

mongo --port 20017 > rs.initiate() > rs.add("shard1.neerajg.in:27010") > rs.add("shard1.neerajg.in:27011")

3. Add data to primary node:

At this point we can add objects to the database and they’ll be replicated to the other instances – and you can read from the primary or the slaves.

1 2	db.people.save( { name : "Neeraj", age: 26, emailid: "[email protected]" } ) db.people.find()

4. Check the log files:

Accessing the log files:

a. Primary Replica Logs (27009):

5. Test failover capabilities:

Now to test failover capabities, do the following:

a. You can either terminate terminal running primary mongodb node or extract process id using the below mentioned command and kill process.

1 2 3

ps -ef | grep mongo kill PID

Generate reports out of the MongoDB data from AWS.

This Quick Start sets up a flexible, scalable AWS environment for MongoDB, and launches MongoDB into a configuration of your choice.

MongoDB is an open source, NoSQL database that provides support for JSON-styled, document-oriented storage systems. Its flexible data model enables you to store data of any structure, and it provides full index support, sharding, and replication.

Use this Quick Start to set up a customizable MongoDB cluster on AWS. You can customize the number of replica sets (1-3), join the replica sets to a sharded cluster, and configure the instance types and Amazon EBS storage attached to the MongoDB nodes.

The Quick Start is for IT infrastructure architects, administrators, and DevOps professionals who want to administer their own MongoDB environment. If you want to set up a fully managed database service instead, you can use MongoDB Atlas. MongoDB Atlas creates a new virtual private cloud (VPC) for your managed databases and automates potentially time-consuming administration tasks such as managing, monitoring, and backing up your MongoDB deployments.

Use this Quick Start to automatically set up the following MongoDB environment on AWS:

• A virtual private cloud (VPC) configured with public and private subnets across three Availability Zones. This provides the network infrastructure for your MongoDB deployment.*
• In the public subnets, NAT gateways to allow outbound internet connectivity for resources (MongoDB instances) in the private subnets.*
• In the public subnets, bastion hosts in an Auto Scaling group with Elastic IP addresses to allow inbound Secure Shell (SSH) access. One bastion host is deployed by default, but this number is configurable.*
• An AWS Identity and Access Management (IAM) instance role with fine-grained permissions for access to AWS services necessary for the deployment process.
• Security groups to enable communication within the VPC and to restrict access to only necessary protocols and ports.
• In the private subnets, a customizable MongoDB cluster with the option of running standalone or in replica sets, along with customizable Amazon EBS storage. The Quick Start launches each member of the replica set in a different Availability Zone. However, if you choose an AWS Region that doesn’t provide three or more Availability Zones, the Quick Start reuses one of the zones to create the third subnet.