Stable timestamp and _currentCommittedSnapshot are redundant

XMLWordPrintableJSON

    • Replication
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: