[SERVER-12666] Replica set moving primary every few minutes Created: 10/Feb/14  Updated: 10/Feb/14  Resolved: 10/Feb/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.4.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Hugo Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

We have a system with 4 nodes, all 4 have DB's and 3 have arbiters.

Two nodes died (simulated testing)(they have 3 votes in total, two DB's and 1 arbiter)

Now the primary keeps moving between the two remaining DB's every few seconds

Mon Feb 10 08:38:09.653 [rsHealthPoll] replSet member 172.29.21.68:27020 is now in state PRIMARY
Mon Feb 10 08:38:49.703 [rsHealthPoll] replSet member 172.29.21.68:27020 is now in state SECONDARY
Mon Feb 10 08:38:57.708 [rsHealthPoll] replSet member 172.29.21.68:27020 is now in state PRIMARY
Mon Feb 10 08:39:49.765 [rsHealthPoll] replSet member 172.29.21.68:27020 is now in state SECONDARY
Mon Feb 10 08:40:27.808 [rsHealthPoll] replSet member 172.29.21.68:27020 is now in state PRIMARY
Mon Feb 10 08:40:49.836 [rsHealthPoll] replSet member 172.29.21.68:27020 is now in state SECONDARY
Mon Feb 10 08:40:57.840 [rsHealthPoll] replSet member 172.29.21.68:27020 is now in state PRIMARY
Mon Feb 10 08:41:49.900 [rsHealthPoll] replSet member 172.29.21.68:27020 is now in state SECONDARY



 Comments   
Comment by Hugo [ 10/Feb/14 ]

Scott

Sorry for this bug. One of my colleagues killed the systems, and I now have no logs.

You can close this as invalid, will relog it if I can replicate it again.

Comment by Scott Hernandez (Inactive) [ 10/Feb/14 ]

Please include the full logs from the nodes which are/have-been primary, rs.status() from all nodes, rs.conf() from a few, and any information about your network/hardware config you know. If you are using MMS, please incude a link to that as well.

Generated at Thu Feb 08 03:29:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.