[SERVER-32045] Propagate addShard writeConcern when sending setFCV to new shard once last_stable is bumped to v3.6 Created: 20/Nov/17  Updated: 30/Oct/23  Resolved: 09/May/18

Status: Closed
Project: Core Server
Component/s: Sharding, Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 4.0.0

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-31866 setFCV should wait for majority commi... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-05-21
Participants:

 Description   

As part of adding a shard, setFeatureCompatibilityVersion is called on the new shard. setFCV was changed to allow writeConcern in v3.6, so when sending setFCV to the shard, the config server should use the writeConcern given for addShard to propagate the user's wTimeout. setFCV doesn't support writeConcern in v3.4 though, and because it is legal to add a v3.4 shard from a v3.6 config server, the CSRS can't propagate the writeConcern until the last_stable version is bumped to v3.6.



 Comments   
Comment by Githook User [ 10/May/18 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-32045 Set write concern on operation context before calling addShard in unittest
Branch: master
https://github.com/mongodb/mongo/commit/b3bc4954c8f9044b92ccfbb4e872f87c69e39016

Comment by Githook User [ 09/May/18 ]

Author:

{'email': 'golden.janna@gmail.com', 'name': 'jannaerin', 'username': 'jannaerin'}

Message: SERVER-32045 Propagate addShard writeConcern when sending setFCV to new shard
Branch: master
https://github.com/mongodb/mongo/commit/b6b9c9a40cebbca123dc7354c6cefb8f856f815b

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