I have a fast Windows 7 PC with 8Gb RAM. I want to test this MongoDB replica set: http://www.mongodb.org/display/DOCS/Replica+Sets for my development. I dont want to buy 3 PCs though, as it's kind of expensive. Is there a way to use some kind of technology, like Hyper-V, to be able to set it up? If not, how many PC and what kind should I buy?
I installed MongoDB in an Ubuntu Server VM inside VMware using these instructions: http://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/. Everything works fine, and I can access MongoDB at the regular port 27017
./mongo 172.16.150.131:27017
Now, I want to make a dummy replica set and another db instance for testing my app.
Our mongodb process is consistently using >100% of our CPU (this is on an Ubuntu 64-bit server on Linode) and we're casting about for performance improvements.
One suggestion we found was that MongoDB and NUMA don't work well together: http://docs.mongodb.org/manual/administration/production-notes/#producti...
I notice that /proc/sys/vm/zone_reclaim_mode is already set to 0 and numactl is no
We using standard mongo setup: 2 replicas + 1 arbiter.
Both replica servers use same AWS m1.medium with RAID10 EBS.
We experiencing constantly growing replication lag on secondary replica.
I've just installed mongodb, and had to install 2.0.4, which I couldn't figure out how to do with 10gen, so followed this tutorial and installed from the tar file.
http://antimalwarelab.com/installing-ubuntu-10-04-1-lts-64-bit-mongodb-2...
Now, in order to start the server, I have to go to ~/mongodb-linux-x86_64-2.0.4/bin and then type ./mongod.
I want to start over the configurations of replica, is it possible? How to reset it?
In group people saying to remove the database content, but are there any work around?
I am trying to install mongodb on Windows 8.
I am using following command to install Mongodb.
C:\mongodb\bin\mongod.exe --auth --config C:\mongodb\mongod.cfg --install
And getting this error:
Wed Mar 13 19:13:23 Trying to install Windows service 'MongoDB'
Wed Mar 13 19:13:23 Error connecting to the Service Control Manager: Access is denied.
I have three servers with mongod installed on it running as a replication set. Suddenly the two secondories became unavailable (the mongod process died) - I think because they were too stale.
The problem is that the original PRIMARY is now the SECONDARY and my application doesn't work because it can't connect to a PRIMARY.
I mean, in which way does that help me?
I have a MongoDB 2.0.4 installation on Ubuntu 12.10. Recently I had some problems connecting to the database from the outside, and figured out there was something which prevented MongoDB from starting correctly. As suggested on several sources (see StackOverflow) I removed /var/lib/mongodb/mongodb.lock and ran mongod --repair.