Very informative discussion about handling master server crashed in MongoDB master/slave setups:
Alvin Richards: in the case of an unclean shutdown, you must always
remove the lock file
start mongod with --repair
after the repair is complete, then you can restart mongod
The time a repair takes is a function of the amount of data and indexes and the I/O capability of your system. Right now you need access to double the amount of storage as the repair takes place. We will be optimizing this going forward. You can use the --repairpath to indicate an alternate volume if you need to provision space just for the repair operation.
This blog is called myNoSQL and it is written by me, Alex Popescu, a software architect with a passion for open source and communities.
It records my readings, learnings, and opinions on NoSQL databases, polyglot persistence, and distributed systems -- subjects that I'm passionate about.
The opinions expressed here are my own, and no other party necessarily agrees with them.
If you feel I'm biased, I probably am.