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

Disable replication recovery invariant that stableTimestamp equals appliedThrough

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.0-rc10
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2, v4.0
    • Sprint:
      Repl 2020-06-15

      Description

      To support downgrade from 4.6 to 4.4 after removal of the stable optime candidates list, which will allow the stable timestamp to be set at a timestamp in the middle of a secondary batch, we should disable this invariant in replication recovery in 4.4. To see if the invariant catches any remaining storage engine bugs in our test infrastructure, we can allow the invariant to be enabled via a failpoint that we will enable in testing.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              william.schultz William Schultz (Inactive)
              Reporter:
              william.schultz William Schultz (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: