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

Stable timestamp and _currentCommittedSnapshot are redundant

    XMLWordPrintable

    Details

    • Linked BF Score:
      0

      Description

      Storage maintains the stable timestamp and replication maintains the _currentCommittedSnapshot (a holdover from the pre-timestamping days). We could reduce replication complexity and possibly gain some performance benefits by only maintaining it in one place (probably storage). If at some point we are able to read consistently at any timestamp, including mid-oplog-application-batch, then both of these values could likely be removed in favor of the replication commit point.

        Attachments

          Issue Links

          depends on

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-34489 Enable new format Unique Index via FCV

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-49777 Change _currentCommittedSnapshot to be a timestamp instead of an optime

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

          Task - A task that needs to be done. SERVER-35420 Remove stable optime candidates list from ReplicationCoordinator

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

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated: