Tag Info

Hot answers tagged

3

Remove the space between the comma and the second IP. It does not look like mongod is handling gracefully.


2

The way I understand it, the hidden secondary will always be behind by the number of seconds defined by slaveDelay. In your case, at any moment in the day, the hidden secondary will always be behind by three hours from the last write to the oplog. If there is no more write activity, then the hidden secondary will be completely caught up in three hours. You ...


2

There are two options PHYSICAL BACKUP If you don't mind downtime, simplest thing to do is service mongod stop Do an LVM snapshot or a brute force cp of the Mongo data folder to another disk service mongod start Of course, you don't want downtime if the 10TB of data is on a standalone machine. DELAYED REPLICA SET If you have a replica set with three ...


2

Yes, you can do this, and in fact with just 2 data centers you really have no other choice. Essentially, whenever you do not have a primary you can still do a reconfig but you must pass in {force:true} to make it happen on a non-primary node. This is listed in the docs for the rs.reconfig() command and in detail (with examples) as part of a tutorial which ...


2

Your query is using the index to fetch the results but needs to sort them afterwards which is an expensive operation. "scanAndOrder" : true, scanAndOrder is a boolean that is true when the query cannot use the order of documents in the index for returning sorted results: MongoDB must sort the documents after it receives the documents from a cursor. The ...


2

For data migration (or backup) between MongoDB servers, you should be using mongodump and mongorestore (binary backups) rather than mongoimport/mongoexport (text backups). Backups (and restores) of sharded collections need to be done through a mongos. There are several reasons to use mongodump/mongorestore: binary backups preserve type fidelity in your ...


1

Just execute on shell "use dbname" When you insert the first document on any collection you will see the db with "show dbs"


1

You can run a --repairDatabase for that node: mongod --repair --repairpath <repair_path> Keep in mind that the repair path should have at least as your data size free disk space. (if you have 100GB, the repair path should have at least 100GB free also. That should take care of problems of that sort. Also, in the future if anything of some sort ...


1

There are two way. opcounters Build as sum of the opcounters which are write operations, build a sum of the opcounters which are read operations set them into relation. To do this reliably for a sharded cluster, you have to create a dashboard which groups the opcounters for the shards. network in/out ratio This is self explanatory. But please keep in ...


1

Your setup is plainly wrong. First, what sense does it make to have automatic failover when your storage system or the connection to it creates a single point of failure? And if you have a storage system which eliminates every single point of failure ( redundancy in power, network interfaces plus network infrastructure, RAID controllers, main boards and ...


1

The upgrade lock record is not removed post upgrade. A "state" of 0 means the lock is not being held. You can ignore or remove manually. The lock definitions for MongoDB 2.6 are available here and are: 0: Unlocked | 1: Locks in contention | 2: Lock held


1

Please read the replication documentation before you go into production. Make sure you have understood them. As per your questions: You don't need config servers, as they are only needed for sharded environments You don't need mongos instances, as they are only needed for accessing shards. You only need an arbiter if you have an even number of data ...


1

With the need of 10TB to be backed up this gets a bit complicated. Replicas are no replacement for proper backups While delayed replica set members can provide an relatively easy way to help you with accidental operations, there are no replacement for proper backups, very much like RAID isn't a replacement for file system based backups. Recommendations ...


1

I suspect you had MongoDB 2.4 installed previously. In MongoDB 2.4 the service was called mongodb and used /etc/mongodb.conf (ref: Install MongoDB 2.4 on Ubuntu). With MongoDB 2.6 there was an attempt to have more standard package names across Linux distributions, so the service was renamed to mongod (to reflect the actual daemon being started) and the ...



Only top voted, non community-wiki answers of a minimum length are eligible