Category: MongoDB

3 Oct by Luis Silva

Monitoring MongoDB Process

  Script to monitor Mongo DB processes across a cluster. [crayon-5c3e71f58f2ba438251661/]   Log file result: [crayon-5c3e71f58f2c0758282543/] Note: Requires ssh passwordless login and cluster configuration file.
21 Sep by Daniel Cruz Tags: , , , , , , ,

How to improve database performance on MongoDB part3

  You should read below articles before reading this article. “How to improve database performance on MongoDB part 1“, “How to improve database performance on MongoDB part 2”   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 […]
4 Sep by Selcen Sahin Tags: ,

MongoDB Resync stale replica member

  In a replica set if one of the members is in RECOVERING state and in the log file of that member if you see: [crayon-5c3e71f58f8da614984979/]   This means that the oplog size wasn’t enough to handle the time that the replica server was unreachable. A network problem, lack of disk space or a closed host may […]
26 Aug by Prabhu Sundarraj Tags: , , , , , , , ,

Hadoop-3.1.0 Multi Node Connection and Configuration in easiest way

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 machine […]
18 Aug by Rabikumar Singh Tags: , , ,

Point in time recovery on Mongodb Standalone server.

  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: , , , ,

Slow queries on MongoDB

  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: […]