[SERVER-49167] Update _setStableTimestampForStorage to set the stable timestamp without using the stable optime candidates set when EMRC=false Created: 29/Jun/20  Updated: 29/Oct/23  Resolved: 09/Jul/20

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

Type: Task Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-49221 Complete TODO listed in SERVER-47844 Closed
is duplicated by SERVER-49355 Complete TODO listed in SERVER-47844 Closed
is duplicated by SERVER-49406 Complete TODO listed in SERVER-47844 Closed
Related
related to SERVER-47844 Update _setStableTimestampForStorage ... Closed
is related to SERVER-49430 Running hang analyzer in awaitSeconda... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-07-13
Participants:

 Description   

We want to set the stable timestamp when enableMajorityReadConcern:false without reliance on the stable optime candidates list. This should continue the work of SERVER-47844. We will not remove any of the logic for computing and updating the stable optime candidates set as a part of this ticket.



 Comments   
Comment by Githook User [ 09/Jul/20 ]

Author:

{'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}

Message: SERVER-49167 Set the stable timestamp without using the stable optime candidates when enableMajorityReadConcern:false
Branch: master
https://github.com/mongodb/mongo/commit/a6cd89a6c4d39b4b21376b109ad335e2fda8fb5d

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