Tag Info

Hot answers tagged

2

For querying secondary run the following command first. After running this, you can do all regular stuff on secondary. rs.slaveOk() To see the replication status, run the following command on primary. This will show you if the secondaries are up to date or lagging. db.printSlaveReplicationInfo() Hope this helps.


2

Since your error is: Failed to restart mongod.service: Unit mongod.service failed to load: No such file or directory. This is pretty much saying that your startup path is not in the expected location or else the Ubuntu install has led to problems. See: http://docs.mongodb.org/manual/tutorial/manage-mongodb-processes/ EDIT: Updated with link to what ...


1

All things being equal, it is logical to assume that better hardware = better performance. However, computers are strange beasts - I know that with Oracle, if you assign very large sizes (you need good hardware) to certain caches, you can actually slow down the machine. The only real suggestion that I have is that you test, test and test again. You cannot ...


1

I ran into a similar issue and found it to be a misconfigured mongod.conf file in my case. It could also be the permissions on the new directory are not set properly. chown -R mongod:mongod <directory name> was how I ensured access (and of course the chmod 600 <dir> as well). Lastly, run an ls -Z to ensure the context is correct. I just ...


1

You can find it through db.serverStatus() on section storageEngine - http://docs.mongodb.org/manual/reference/command/serverStatus/#storageengine


1

MongoDB does not currently support a multi-master setup such as you describe. If you were looking to provide localized regional writes via MongoDB, your best bet is to setup a sharded collection, using shard tag ranges. You would have 1 (or more) shard per region, with the primary residing within the region it manages and remote secondaries. Region would ...


1

Nothing bad happened even if you took the config server offline during a chunk migration. In order for a chunk to be marked as migrated, all three config servers need to be up (Contrary to popular belief they do not form a replica set.). (The following is a tiny bit simplified for the sake of shortness.) When a chunk is moved, a global (read cluster wide) ...


1

3 different things. Hadoop is a framework. Something you use to develop an entire application. MongoDb is a db. A nosql one. It is where you store data. BigData is a concept. It is related to huge quantity of data. Where huge is not a fixed parameter. 4 mb was huge in 1960. Now huge means several terabyte.


1

There is a tool on CodePlex you can use for this, called MSSQL to MongoDB Tool. This tool will migrate all data from MSSQL to MongoDB. It will do this without exporting to a file first. If you want to export to file first, you are best off using the Export Data wizard which you can find in your SSMS, by right clicking your DB and choose 'Export Data' under ...



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