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

WT clean shutdown should do a quick exit before shouldDowngrade() check if the node is still not safe to take stable checkpoints.

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl 2020-05-18
    • 50

      Currently, we would be able to take stable checkpoints when stable timestamp < initial data timestamp if the WT files needs to be downgraded on shutdown. This can result in data corruption (like SERVER-38925).

      As part of this git commit hash (SERVER-47219), we moved the stable & initial data timestamp comparison check before downgrade check. Unfortunately, this fix is present only in 4.4. and not in master (> mongoDB 4.4 version).  This ticket would forward port only the C++ changes (and not test changes) present in this git commit.

            Assignee:
            suganthi.mani@mongodb.com Suganthi Mani
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: