Resync MongoDB member

Method of Procedure

Valid from

Version 11.03.03.000.00

©RADCOM Ltd., 2018

© 2018 RADCOM Ltd. ALL RIGHTS RESERVED.

This document and any and all content or material contained herein, including text, graphics, images and logos, are either exclusively
owned by RADCOM Ltd., its subsidiaries and/or affiliates ("RADCOM") or are subject to rights of use granted to RADCOM, are protected by
national and/or international copyright laws and may be used by the recipient solely for its own internal review. Any other use, including
the reproduction, incorporation, modification, distribution, transmission, republication, creation of a derivative work or display of this
document and/or the content or material contained herein, is strictly prohibited without the express prior written authorization of
RADCOM.

The information, content or material herein is provided "AS IS", is designated confidential and is subject to all restrictions in any law
regarding such matters, and the relevant confidentiality and non-disclosure clauses or agreements issued prior to and/or after the
disclosure. All the information in this document is to be safeguarded and all steps must be taken to prevent it from being disclosed to any
person or entity other than the direct entity that received it directly from RADCOM.

The text and drawings herein are for the purpose of illustration and reference only.

RADCOM reserves the right to periodically change information that is contained in this document; however, RADCOM makes no
commitment to provide any such changes, updates, enhancements or other additions to this document to you in a timely manner or at all.

Publication Date: Jun 2018

Document Version: v1.1

Web Site:
http://www.radcom.com
 Table of Contents
Preface.........................................................................................................................................2
1. Document Overview...............................................................................................................2
2. Reference Documents............................................................................................................2
3. Revision History......................................................................................................................2
Procedure Overview.....................................................................................................................2
4. Limitations or Considerations.................................................................................................2
5. Description of Resync steps....................................................................................................3
5.1 Stop the member’s process......................................................................................................3
1. Identify the MongoDB “stale” secondary member’s IP...........................................................3
5.2 Delete member’s data from dbPath directory..........................................................................3
1. On the same VM from previous step, find the data directory as configured in
/etc/mongod.conf..............................................................................................................................3
3. Delete all data and sub-directories from this dbPath directory..............................................3
 Preface
1. Document Overview
This document describes the procedure for resyncing MongoDB replica set member which is part of MaveriQ
System.

2. Reference Documents

3. Revision History
The following table provides the revision history of Resync_MongoDB_Member MOP.

Rev Date Author Description Reviewed Approved

by by

1.0 06/29/2018 Einat Stern First Draft

Chai
1.1 07/05/2018 Einat Stern Changes according to Oleg’s
Chai review. Added commands for
mongo watchdog in crontab

Procedure Overview
A replica set is a cluster of MongoDB servers that implement replication and automated failover. A member
that it’s replication process falls behind and cannot catch up becomes “stale”. The member indicated state in
this case might be either “RECOVERING” or “UNKNOWN”.
When this is the situation, a manual intervention is required to completely resynchronize the member. This
is done by removing the member’s data and performing a method for “Automatically Sync a Member”,
which relies on MongoDB regulator process of Replica Set Syncing, to store current data on the member.
Therefore, the procedure consists of 3 main steps:
 Stop the member’s process
 Delete member’s data from dbPath directory
 Start the member’s process

4. Limitations or Considerations

Resyncing a stale member uses seed data from another member. Schedule this synchronization during a
time of law usage of the system to allow moving large amount of data.

2
5. Description of Resync steps
5.1 Stop the member’s process

1. Identify the MongoDB “stale” secondary member’s IP

2. Login to that VM as user deployment and switch to user root (sudo su -)
3. Use the following commands to cleanly and safely terminate the mongod process:
 Edit crontab
crontab -e
 Comment out the command which starts mongod server
Before:

After:

 Save the crontab file and exit

 Stop mongod service
service mongod stop

5.2 Delete member’s data from dbPath directory

1. On the same VM from previous step, find the data directory as configured in /etc/mongod.conf.
grep dbPath /etc/mongod.conf

2. Change to the directory indicated in the configuration file.

cd /data/mongodb

3. Delete all data and sub-directories from this dbPath directory.

\rm -rf /data/mongodb/*

3
5.3 Start the member’s process
1. On the same VM from previous step, issue the following commands to start the mongod service:

 Start service
service mongod start

 Edit crontab
crontab -e
 Uncomment the command which starts mongod server
Before:

After:

 Save the crontab file and exit

2. Continue to verify the state of the resynced member until it’s back to “SECONDARY”
 Connect to MongoDB CLI
mongo