|
umputun, looks like you've run into SERVER-17613, which may happen after an unclean shutdown.
SERVER-17613 is fixed in the upcoming 3.0.2 release, but since we haven't published it yet here's a workaround to allow you to get past this problem:
- Download a recent nightly build on the v3.0 branch
- Temporarily replace your 3.0.0 binary with the one from the nightly build
- Start your MongoDB instance with this new binary, and then do a clean shutdown by running db.shutdownServer() in the shell
- Revert back to the 3.0.0 binary
The alternative, which may take longer but is much simpler, is to wipe out the data in this secondary and resync the data from the primary.
|