[SERVER-47870] Push updated majority commit point values on config servers into configOpTime Created: 01/May/20  Updated: 29/Oct/23  Resolved: 04/May/20

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Kevin Pulo
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-46200 Implement a VectorClockService Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-05-18
Participants:

 Description   

Currently there is no in-memory value of configOpTime maintained on config servers (unlike shards/mongos), and instead when config servers gossip out configOpTime they just pull the latest commit point value from repl. In order to normalize the handling of configOpTime (mostly in SERVER-46200), relative to other logical/vector clocks in the system, we would like to push the new commit point optime into an in-memory location on config servers when replication notices that it has been updated.



 Comments   
Comment by Githook User [ 04/May/20 ]

Author:

{'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}

Message: SERVER-47870 Push updated majority commit point values on config servers into configOpTime
Branch: master
https://github.com/mongodb/mongo/commit/e39ec9be74984c60337db640269219c7433abbc2

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