[SERVER-4685] Arbiter fails to respect priority in 2 read/write node 1 arbiter setup Created: 15/Jan/12  Updated: 15/Aug/12  Resolved: 03/Mar/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.0.1, 2.0.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Justin Wiley Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: replication
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux TELL02VMW01 2.6.32-37-server #81-Ubuntu SMP x86_64 GNU/Linux


Operating System: Linux
Participants:

 Description   

I've been trying to setup a simple replication system. 1 main mongo, 1 backup, and 1 arbiter.

Unfortunately, firing it up lead to main being elected SECONDARY, and the backup being elected PRIMARY.

Main priority set to 100, and backup a priority of 0, along with a slave delay of 3600.

Downing backup leads to main being elected PRIMARY, but when backup is brought back on line, it resumes its spot as PRIMARY. Main then enters RECOVERING mode, and never recovers.

hidden = true has no effect on this behaviour.

More details including various config files:

http://stackoverflow.com/questions/8858831/trying-to-setup-mongo-replication-but-end-up-with-two-secondary-members-and-no/8858940#8858940

This was eventually solved by reinstalling all of the relevant servers.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 18/Jan/12 ]

Do you have the rs.conf()?

Comment by Justin Wiley [ 15/Jan/12 ]

By "reinstalling all of the relevant servers" I mean deleting the data directories and reinstalling mongo db via the packages.

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