[SERVER-34166] Stop writing config server connection string and shard name to minOpTime recovery document Created: 28/Mar/18  Updated: 29/Oct/23  Resolved: 26/Jun/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jason Zhang
Resolution: Fixed Votes: 0
Labels: neweng, sharding-interns-2019
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-25276 Remove code for parsing and handling ... Closed
Backwards Compatibility: Minor Change
Backport Requested:
v4.2
Sprint: Sharding 2019-07-01
Participants:

 Description   

We stopped using these fields in 3.6, but we still parse the minOpTime recovery document expecting to find them, returning a bad status if we can't. In 4.0, we stopped parsing these fields, but continued to write them, so when downgrading, a 3.6 node won't crash during sharding state recovery. After 4.0 ships, we can stop writing these fields.



 Comments   
Comment by Githook User [ 26/Jun/19 ]

Author:

{'name': 'Jason Zhang', 'email': 'jz1242@gmail.com', 'username': 'jz1242'}

Message: SERVER-34166 Stop writing config server connection string and shard name to minOpTime recovery document.
Branch: master
https://github.com/mongodb/mongo/commit/d55af602375de9142b9940b02a4d2604f8a77477

Comment by Jason Zhang [ 25/Jun/19 ]

Patch Build: https://evergreen.mongodb.com/version/5d113697a4cf47485aecebab

 

Code review: https://mongodbcr.appspot.com/459320002/

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