Your production sharded cluster has lots of chunks with a jumbo flag w

1.	Your production sharded cluster has lots of chunks with a jumbo flag which is hampering application performance. How will you clear the jumbo flag?
Answer» The OPLOG is operation logs that keep an update of all operations that modify the data stored in databases. We can define the oplog size while STARTING MongoDB by specifying the --oplog option. If we do not specify this option it will take the default values which is 5% of PHYSICAL memory in case of wiredTiger. While the default value is sufficient for most workloads in some cases we may need to change the oplog size for the replica SET. OPlog size is CHANGED in a rolling manner, first, we change on all secondary and then a primary member of the replica set. To change oplog size First we need to connect to any secondary member. Verify the size of current oplog by running below command on the local database. use local db.oplog.rs.stats().maxSize Change the oplog size using admin command replSetResizeOplog specifying a new size for oplog. db.adminCommand({replSetResizeOplog: 1, size: "Size-in-MB"}) Repeat the same process for other secondary members and then on the primary member of the replica set.

Your production sharded cluster has lots of chunks with a jumbo flag which is hampering application performance. How will you clear the jumbo flag?

Answer»

The OPLOG is operation logs that keep an update of all operations that modify the data stored in databases. We can define the oplog size while STARTING MongoDB by specifying the --oplog option. If we do not specify this option it will take the default values which is 5% of PHYSICAL memory in case of wiredTiger. While the default value is sufficient for most workloads in some cases we may need to change the oplog size for the replica SET.

OPlog size is CHANGED in a rolling manner, first, we change on all secondary and then a primary member of the replica set. To change oplog size

First we need to connect to any secondary member.
Verify the size of current oplog by running below command on the local database.

use local

db.oplog.rs.stats().maxSize

Change the oplog size using admin command replSetResizeOplog specifying a new size for oplog.

db.adminCommand({replSetResizeOplog: 1, size: "Size-in-MB"})

Repeat the same process for other secondary members and then on the primary member of the replica set.

Your production sharded cluster has lots of chunks with a jumbo flag which is hampering application performance. How will you clear the jumbo flag?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment