[SERVER-50675] Get rid of Grid's configOpTime after 5.0 has branched out Created: 01/Sep/20  Updated: 29/Oct/23  Resolved: 29/Jul/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-29729 remove afterOpTime readConcern argument Backlog
is depended on by SERVER-54252 Cleanup legacy configOpTime gossiping Closed
Duplicate
is duplicated by SERVER-44097 Remove term from config server opTime... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-08-09
Participants:

 Description   

Remove this FCV check and its uses.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 29/Jul/21 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-50675 Get rid of Grid's configOpTime after 5.0 has branched out
Branch: master
https://github.com/mongodb/mongo/commit/e81cb3762287d565644a96d2891d7d8ad820f1b0

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