[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: |
|
||||||||
| 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 |
| Comments |
| Comment by Githook User [ 04/May/20 ] |
|
Author: {'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}Message: |