I have a replicaset that processes largish batches of inserts (a few million) every night. Last night, the primary failed over and went into a rollback state. All clients which access this replicaset use a connection URL with w=majority. The mongo DB documentation states that this should be sufficient to stop the old primary entering the rollback state. The old primary was in the rollback state for a solid 45 minutes.

Am I missing something in the config to ensure this doesn't happen?

  • Do you have journaling enabled? – SqlWorldWide Oct 19 '19 at 18:35
  • @SqlWorldWide I thought journaling was enabled by default (I didn't even know you could turn it off) – Zack Newsham Oct 20 '19 at 2:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.