[SERVER-6661] should we allow this reconfig case for replica sets? Created: 31/Jul/12  Updated: 15/Aug/12  Resolved: 31/Jul/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.2.0-rc0
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: Dwight Merriman Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

i don't see why not, is there a nuance? i am sending the reconfig to the current primary. however it isn't eligible thereafter. doesn't this mean if you want to "flip/flop" priority 0 and 1 on a 2 member set, it is impossible to do that?

i stepped down, went to the other one, reconfiged, as a workaround.

x:PRIMARY> cfg = rs.conf()
{
        "_id" : "x",
        "version" : 2,
        "members" : [
                {
                        "_id" : 0,
                        "host" : "dm_hp:27017"
                },
                {
                        "_id" : 1,
                        "host" : "dm_hp:27000"
                }
        ]
}
x:PRIMARY> cfg.members[1].priority=0
0
x:PRIMARY> cfg
{
        "_id" : "x",
        "version" : 2,
        "members" : [
                {
                        "_id" : 0,
                        "host" : "dm_hp:27017"
                },
                {
                        "_id" : 1,
                        "host" : "dm_hp:27000",
                        "priority" : 0
                }
        ]
}
x:PRIMARY> rs.reconfig(cfg)
{
        "errmsg" : "exception: initiation and reconfiguration of a replica set must be sent to a node that can become primary",
        "code" : 13420,
        "ok" : 0
}
x:PRIMARY>



 Comments   
Comment by Dwight Merriman [ 31/Jul/12 ]

disregard this was mixed version testing and likely doesn't happen anymore???

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