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

Consider removing minValid timestamp and term fields once enableMajorityReadConcern:false is removed

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication

    Description

      Once rollbackViaRefetch is removed, which should be possible on enableMajorityReadConcern:false is removed, we should no longer have a need for the minValid optime. If we crash during secondary oplog application, we will always recover to a stable timestamp which was set at a timestamp where a complete batch had already finished, so we don't require it for crash resilience in this case. Similarly, recover to a timestamp always recovers to a consistent state post rollback, so we never go through a phase of inconsistency while waiting to reach a minValid timestamp.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            william.schultz@mongodb.com William Schultz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: