[SERVER-15220] Reconfiguring a replica set member with 2 votes causes a fatal assertion crash Created: 11/Sep/14  Updated: 25/Oct/14  Resolved: 21/Oct/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.7.6
Fix Version/s: 2.7.8

Type: Bug Priority: Major - P3
Reporter: Timothy Olsen (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File 2-votes-fatal-assertion.log    
Issue Links:
Tested
Backwards Compatibility: Minor Change
Operating System: ALL
Steps To Reproduce:

Start up and configure a 2.7.6 replica set
Reconfigure one of members to have 2 votes

Participants:

 Description   

Log file attached



 Comments   
Comment by Spencer Brody (Inactive) [ 21/Oct/14 ]

Seems to have gone away (as expected)

> var conf = rs.conf()
> conf.members[0].votes = 2
2
> rs.reconfig(conf)
{
	"ok": 0,
	"errmsg": "votes field value is 2 but must be 0 or 1",
	"code": 93
}

Comment by Eric Milkie [ 11/Sep/14 ]

I believe this is simply due to the interim support of both the old and new config code, and that by the time we release 2.8 this issue will resolve itself. We should check to make sure this is the case, and possibly create a jstest for it.

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