[SERVER-1577] when adding arbiter the PRIMARY fails to SECONDARY immediately Created: 05/Aug/10  Updated: 12/Jul/16  Resolved: 24/Aug/10

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 1.6.0
Fix Version/s: 1.6.3, 1.7.0

Type: Bug Priority: Minor - P4
Reporter: Kenny Gorman Assignee: Dwight Merriman
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

linux x64


Operating System: ALL
Participants:

 Description   

When adding arbiter, immediately the PRIMARY goes to SECONDARY.

Steps:

  • create new 2 node cluster.
    config=
    Unknown macro: {"_id"}

    rs.initiate(config)

  • add arbiter
    rs.addArb("al05:27017");

here is a log of the action:
http://gist.github.com/510474



 Comments   
Comment by auto [ 15/Sep/10 ]

Author:

{'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}

Message: SERVER-1577 stay primary on some config changes
http://github.com/mongodb/mongo/commit/db296d0ef86944a02164696cbafa8ff0a001cdf0

Comment by auto [ 15/Sep/10 ]

Author:

{'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}

Message: towards SERVER-1577 reconf without losing primary status
http://github.com/mongodb/mongo/commit/6fb9fbe207d1c7849b1eae0b650991e8109b0752

Comment by auto [ 15/Sep/10 ]

Author:

{'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}

Message: towards SERVER-1577 reconf without losing primary status transiently
http://github.com/mongodb/mongo/commit/2fe3e06391ceb6426a98aaf5ae8289b438a1da67

Comment by auto [ 09/Aug/10 ]

Author:

{'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}

Message: SERVER-1577 stay primary on some config changes
http://github.com/mongodb/mongo/commit/926bf4bd0ed5370b0bc8dd3f07b37f63011dcdc7

Comment by auto [ 08/Aug/10 ]

Author:

{'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}

Message: towards SERVER-1577 reconf without losing primary status
http://github.com/mongodb/mongo/commit/db2dfba94c421d64193b1067f8b6ed881e237479

Comment by auto [ 07/Aug/10 ]

Author:

{'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}

Message: towards SERVER-1577 reconf without losing primary status transiently
http://github.com/mongodb/mongo/commit/8460ae83c70487a3060ed56539d06925cfc2ffc4

Comment by Dwight Merriman [ 06/Aug/10 ]

yes - this is as planned for 1.6.0. when the config changes there is a new negotiation of who is primary. this results in 20 seconds or so of rediscovery.

some of these things will be better in 1.6.1 and 1.6.2. the plan with 1.6.0 was to avoid mistakes with edge cases, as config changes will be very rare anyway, and there are some edge cases where the primary actually should change with a new arbiter in place (unusual).

working on it.

Generated at Thu Feb 08 02:57:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.