Reputation
3,079
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
7 32
Newest
 Revival
Impact
~115k people reached

May
30
answered MongoDB is not using all of my system memory for working set?
May
27
answered What causes SocketException (9001) handling request in node.js app and MongoDB ReplicaSet?
May
23
answered Cannot Restart MongoDB 2.4.3 on Debian 6.0.7 (32-bit)
May
22
answered MongoDB Locking - Very, very, slow to read
May
22
answered mongodb mystery crashes with sigkill under strace
May
14
awarded  Caucus
May
14
comment Mongodb production server too slow compared to staging
you can add this as an answer (and perhaps add a bit of detail about how you identified the culprit) and accept the answer yourself once enough time has gone by - I'll upvote it - knowing that whoopsie can go nuts is important :)
Apr
30
comment mongodb mystery crashes with sigkill under strace
Any chance that this is an Amazon VM?
Apr
25
comment Strange behaviour starting process with init script
In that case, the patch I mentioned above (which essentially stops the script from using numactl) should be a valid workaround for you until we fix the root issue with the bug. Just be aware that the init script may get overwritten if you upgrade at a later date.
Apr
24
comment Strange behaviour starting process with init script
ah, then numactl is installed (detected by the init script) but I believe the Linode instances are Xen VMs so I think you are OK. If in doubt, have a look here: serverfault.com/questions/471204/…
Apr
23
comment Strange behaviour starting process with init script
I think you are hitting the bug I added to the answer, looks like a numactl related issue. If you are on a non-NUMA machine, you could take a look at the patch here: jira.mongodb.org/browse/SERVER-8774 (for a NUMA enabled machine you should make sure mongod is run with numactl).
Apr
23
revised Strange behaviour starting process with init script
added a note about the relevant bug
Apr
23
answered Strange behaviour starting process with init script
Apr
22
answered Mongodb sharding - Init script for mongos process?
Apr
8
revised How to get the MongoDB' current working set size
Added note about 2.4 new feature
Mar
13
comment MongoDB default port change
you can also pass it as an argument to the binary in the upstart script as --port 9999 - exact same effect, but thought I would mention it as an alternative
Mar
8
answered Fresh MongoDB Using 100MB of Virtual Memory?
Mar
5
comment MongoDB: two nodes & primary election
actually, it does answer the question - 2/3 = majority, 2/2 = majority. The difference is that in a 3 node set if you lose a node you still have a fully functioning primary and a secondary, in a 2 node set if you lose a single node you are read only (no primary). You can run with 2 nodes, it just doesn't get you anything from a redundancy perspective - in fact you have made your system more likely to fail.
Feb
22
comment Mongodb keeps reporting “no primary found”, but shell works fine
Then I am going to guess that you have configured the driver incorrectly and that it can't connect to the primary at all. Is the client on a different host? If so, run a mongo shell from that host and try to connect to exactly what you have configured in the driver.
Feb
22
comment Mongodb keeps reporting “no primary found”, but shell works fine
it's not just sub-optimal, it's actually worse than having a single node, so if you simply turned off the arbiter and reconfigured to just a primary you would have a better set up than you do now