The story—a quite long and interesting one—of moving a MongoDB collection from one cluster to a new one:
While MongoDB allows you to add shards to a MongoDB cluster easily, we
wanted to spare ourselves potential long-term pain by moving one of the most
frequently updated MongoDB collections, which stores email-related data, to
its own cluster. We theorized that this would, at a minimum, cut the amount
of write lock contention in half. While we could have chosen to scale by
adding more shards, we wanted to be able to independently optimize and
administer the different types of data separately.
I’m not an ops person and I don’t know what the optimal process is. Hopefully readers will share their expectations.
Original title and link: Scaling MongoDB at Mailbox ( ©myNoSQL)