Documentation here says three:
http://docs.mongodb.org/manual/tutorial/deploy-replica-set/
"A replica set requires three distinct systems..."
Whereas the documentation here says two:
http://docs.mongodb.org/manual/core/replication/
"Most replica sets consists of two or more mongod instances..."
Anyone know which is correct?
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.
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?
Possible Duplicate:
Can you help me with my capacity planning?
I am contemplating purchasing/setting up a 16gb server which will contain 2 5gb instances of mongodb (multi drive replica/shard sets with remote backup with slave reads ok), a 4gb redis instance and a 2 gb postgres instance.
As you can see, my two Windows Server Failover Cluster (WSFC) nodes have three network interfaces each, which connects them to three different networks :
A public network
A private network consisting of the WSFC nodes
A private network consisting of the WSFC nodes and a machine with the WSFC Quorum Witness File Share
Does this network configuration I've planned, make sense?
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
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 am looking at adopting a Mongo cluster and am doing research.
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.