Tag Info

New answers tagged

3

The server crashed for me if you send SIGUSR1 to mongod after you have moved the logfile out of the way with logrotate. The following config is safe for the version I've tested - 2.6.6 on ubuntu 12.04 - the previous examples crashed the server. Put this into /etc/logrotate.d/mongod: /var/log/mongodb/mongodb.log { weekly missingok rotate 4 ...


2

It's probably /dev/sdb given the sizes you listed, but you can find out by running df -h. I keep my data in /data and here is my relevant output: > df -h Filesystem Size Used Avail Use% Mounted on /dev/sdb1 70G 18G 49G 27% / /dev/sdc1 932G 682G 250G 74% /data In my case that means that the one I should be altering for ...


0

Apart from the manual configuration and AMI configuration you can use a deployment service like Deploy4Me. It is just a better way to configure AWS. You can configure Ruby and MongoDB to be installed on the same server. So, you would receive a fully configured environment with some extra perks like security and proper Linux configuration.


1

Only indexes that were created with {background: true} originally (and hence have that option set in the system.indexes collection) are built in the background once restored. Once you have the database dumped you will have your data in the name.bson file and the metadata (indexes to build) in the name.metadata.json file. Unlike the BSON file, the JSON ...


0

We managed to solve this by using other tools than mongodump / mongorestore. Going with the dropbox hydra project (https://github.com/dropbox/hydra) went much faster and smoother to copy the whole database and keep in sync our new cluster. Dunno if it's the tools Markus was going to suggest in comments, but they work fine :) Still no clues why mongo tools ...


2

For now at least, they are basically equivalent, assuming the mongod is not doing anything else significant. To explain, in versions 2.6 and below, the mongorestore utility effectively contains the mongod binary which allows it to act as a mongod and insert to data files without a mongod running already. The advantage a solo mongorestore usually has is ...


0

I decided to keep this up in case someone else runs into the same problem. The problem was that I was using: mongod when I should have been using: mongo


0

That's pretty easy: simply add the host instance in MMS using add host in the deployment tab. Everything else should work automagically.



Top 50 recent answers are included