[SERVER-26811] FeatureCompatibilityVersion::set should check if node can accept writes Created: 27/Oct/16  Updated: 31/Oct/16  Resolved: 28/Oct/16

Status: Closed
Project: Core Server
Component/s: Internal Code, Querying
Affects Version/s: 3.4.0-rc1
Fix Version/s: 3.4.0-rc2

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: David Storch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Query 2016-11-21
Participants:
Linked BF Score: 0

 Description   

If the primary config server stepped down in the middle of ConfigSvrSetFeatureCompatibilityVersionCommand, FeatureCompatibilityVersion::set will still be called. This triggers an fassert in logOp.

It looks like the fassert can be avoided if the command does a canAcceptWritesFor check when doing writes.



 Comments   
Comment by Githook User [ 28/Oct/16 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-26811 fix setFeatureCompatibilityVersion to raise a user assertion if a stepdown occurred
Branch: master
https://github.com/mongodb/mongo/commit/c430494e34cc459d1b17ddcdda79190462b79ee9

Generated at Thu Feb 08 04:13:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.