9 Oct
by Luis Silva
Script to monitor Health Instance on MongoDB Cluster [crayon-5bf195ac0bc04113426865/] Note: Requires username and password with RootPrivileges.
3 Oct
by Luis Silva
Script to monitor Mongo DB processes across a cluster. [crayon-5bf195ac0c013497308667/] Log file result [crayon-5bf195ac0c019970229458/] Note: Requires ssh passwordless login and cluster configuration file.
21 Sep
by Daniel Cruz
Tags: Configuration, FileSystems, MMAPv1, MongoDB, noatime, NUMA, READAHEAD, WIREDTIGER
3 Ensure you have the right configuration The default configurations are not optimal for MongoDB. Must be applied some changes. NUMA: Many modern multiprocessors have non-uniform memory access (NUMA) memory designs, where the performance of a process can depend on whether the memory range being accessed is attached to the local CPU or to another […]
4 Sep
by Daniel Cruz
Tags: cache_size, MongoDB, ram, serverStatus, WireTiger
2 Ensure you have enough RAM. As other Database Managers, MongoDB performs best when the portion of your data that clients access most often live in RAM. RAM size is the most important factor for hardware. To calculate how much RAM you need, you must calculate your working set size or the portion of your data that clients use […]
4 Sep
by Selcen Sahin
Tags: MongoDB, replica
Hi, In a replica set if one of the members is in RECOVERING state and in the log file of that member if you see: 2018-02-14T16:02:50.410+0300 E REPL [rsBackgroundSync] too stale to catch up — entering maintenance mode 2018-02-14T16:02:50.410+0300 I REPL [rsBackgroundSync] our last optime : (term: 32, timestamp: Jan 12 22:42:48:1c51) 2018-02-14T16:02:50.410+0300 I REPL [rsBackgroundSync] oldest […]
29 Aug
by Daniel Cruz
Tags: Encrypted, In-Memory, Storage engine, WIREDTIGER
This little guide is medium in scope, it is not exhaustive. It just gives you an idea to focus 1 Choose the right storage engine for your specific workload. The storage engine is the component of the database that is responsible for managing how data is stored, both in memory and on disk. Comparative: Storage […]
26 Aug
by Prabhu Sundarraj
Tags: big data, Data Analytics, hadoop, hadoop 3.1 multi node connection using centos 7, hadoop multi node, hadoop-3.1.0, multi node, multi node cluster configuration, multinode
HADOOP MULTI NODE INSTALLATION PROCESS [ Note: I am creating multi node in most easiest way by creating and using everything in root mode on default users like (master, slave1, slave2…etc). Please don’t create any hadoop users like (hadoop, hduser, …etc) to configure and share hadoop installations. I am using root user in all […]
21 Aug
by Daniel Cruz
Tags: collection, database, Fragmentation, Index, MMAPv1, MongoDB, Storage engine, WIREDTIGER
Fragmentation on MongoDB databases When we removing a large amount of data from the collection and no plan to replace it, we generate a fragmentation, to deal with it, we have a COMPACT command. The compact command rewrites and defragments all data and indexes in a collection, depending on what storage engine we have. […]
18 Aug
by Rabikumar Singh
Tags: Database Recovery, Database Recovery Models, MongoDB, MongoDB Log
1:- Enable oplog using –master option while starting mongod service [Version 3.2]. And later version (3.2 +) need to put replSetName=rs0 into the mongo.conf file in replication section. Note :- Version 3.2+ after enabling oplog by putting replica set name into the conf file, Need to take login in mongo and run command rs.intiate() and fire […]
14 Aug
by Daniel Cruz
Tags: locks, MMAPv1, MongoDB Log, MongoDB performance, slowms
During a typical revision of mongod’s logs, we could find slow queries, by default, those queries that take more >100ms. You can change this time with –slowms <integer> parameter when you launch a mongod process or using a configuration file. This is an expample of log message: 2018-07-02T12:26:24.580-0500 I COMMAND [conn11186210] command test.CARcommand: getMore { getMore: 164459457945, collection: […]
