Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-47844

Update _setStableTimestampForStorage to set the stable timestamp without using the stable optime candidates set when EMRC=true

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.7.0
    • Replication
    • None
    • Fully Compatible
    • Repl 2020-05-18, Repl 2020-06-01, Repl 2020-06-15, Repl 2020-06-29, Repl 2020-07-13
    • 15

    Description

      Currently, we update the stable timestamp inside ReplicationCoordinatorImpl::_setStableTimestampForStorage by computing the stable optime from the set of stable optime candidates. We should remove the dependence on the stable optime candidates for setting the stable timestamp and updating the committed snapshot when enableMajorityReadConcern:true. We should be able to set the stable timestamp for storage directly as min(all_durable, lastCommittedOpTime). We will not remove any of the logic for computing and updating the stable optime candidates set as a part of this ticket.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. SERVER-49472 Add back holdStableTimestampAtSpecificTimestamp failpoint that was removed from runnable code path

          • Major - P3 - Major loss of function.
          • Closed
          depends on

          Task - A task that needs to be done. SERVER-49006 Only advance oldest timestamp when setting lastApplied during initial sync instead of STARTUP2 state

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-48518 Rollback via refetch (EMRC = false) can make readers to see the rolled back data even after the rollback node catches up to primary.

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-47845 Remove obsolete code related to storing and updating stable optime candidates

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-33806 Oldest timestamp can move ahead of the commit point.

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-30577 Clear list of stable timestamp candidates on Rollback and Initial Sync

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-33292 Have storage dictate where replication recovery should begin playing oplog from

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-49167 Update _setStableTimestampForStorage to set the stable timestamp without using the stable optime candidates set when EMRC=false

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-55305 Retryable write may execute more than once if primary had transitioned through rollback to stable

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-49221 Complete TODO listed in SERVER-47844

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-49355 Complete TODO listed in SERVER-47844

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-49406 Complete TODO listed in SERVER-47844

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              william.schultz@mongodb.com William Schultz (Inactive)
              william.schultz@mongodb.com William Schultz (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: