@mediocregopher Re: replica sets. You don't need config servers to run replica sets. You need config servers to run a sharded cluster. Your understanding of wh

@mediocregopher Re: replica sets. You don't need config servers to run replica sets. You need config servers to run a sharded cluster. Your understanding of when to run an arbiter is also flawed. I think you might find the documentation enlightening: http://docs.mongodb.org/manual/ http://docs.mongodb.org/manual/. The unfortunate situation you describe where the master was left in a read-only state is a flawed setup -- not an error in mongo. In your second paragraph referring to "random occurrences" you're again conflating sharding and replica sets... I'm not sure what exactly you're describing, sorry :(! IN general you should not ignore errors in logs... the mongo processes all have log rotation via signals or server commands. I think a lot of what you're describing is hard to take at face value because of a lack of a common vocabulary -- or some misunderstanding. In my experience mongo has worked fairly well in some large scale systems. It's not the solution to everything -- I'll agree with that... but if you read the documentation it does what you would expect.