When using the MMAPv1 storage engine, a race condition during the transaction rollback of oplog insertions may result in a crash.
MongoDB may crash and corrupt oplog. Primary re-election may not occur. Heavy insert loads increase the likelihood that this race condition may impact the system.
This behavior has been observed when balancing a collection that has large objects and when the chunk migration "source" mongod is under heavy load.
There are no workarounds for this issue.
Following a crash execute
to ensure a reelection occurs.
MongoDB 3.0.0 through 3.0.8
The fix is included in the 3.0.9 release.