I have a replica set with 2 members and 1 arbiter. The data center hosting the Secondary was having intermittent network issues today, which caused the Secondary to go down several times, often up/down a few times within a minute.

To my surprise, at a certain point this caused the Primary to go to ROLLBACK state bringing the whole replica down, even though the Primary and Arbiter had no connectivity issues.

The ROLLBACK state persisted for several minutes, until I restarted the DB service and removed the faulty Secondary from the replica set.

What caused this behavior and how can I prevent this from happening?

If I replace the Arbiter with another member, will this make things more reliable?

  • 1
    Could you post the output of rs.conf() and your MongoDB version – kevinadi Jan 6 '17 at 5:43
  • 1
    please provide also mongodb.log from the time frame network outage of all nodes. – Ivanov Jan 9 '17 at 14:22
  • I faced a similar issue, i have posted the question along with logs and configs here - dba.stackexchange.com/questions/206664/… – Awanish Raj May 14 '18 at 13:02

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.