Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If I start with Mongodb on a single server, but foresee that I need to scale out, should I configure it in any specific way? I guess I am looking for tips from people who have gone down this route.

share|improve this question
up vote 3 down vote accepted

No, Replica Sets and Sharding (the two methods of scaling and redundancy) do not require any special treatment to occur on the solo db so that you may later add them in. In fact, adding replication is reasonably painless and straight-forward. (Sharding does require a little more effort, but is still pretty easy.)

share|improve this answer
Ok thanks gWaldo – Mark Apr 19 '12 at 8:06
I'd suggest a minor edit to the answer: the only "special treatment" to the solo database server instance would to be to restart it in "replica set mode" and initiate a replica set config on it. Similar handling for sharding. Both are easy, and fairly well documented. – Mike Fiedler Apr 22 '12 at 12:50
That is only once the decision to make it a replica set. Until then, nothing needs to be done. – gWaldo Apr 23 '12 at 16:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.