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

Fix read_only_test.js to avoid start point beyond end point during replication recovery.

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.3, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v5.0
    • Repl 2021-08-09
    • 28

      read_only_test.js can hit an the uassert because the start point of the recovery is beyond the end point. The end point is provided by the test, which is the operation time of some previous writes. The start point is the WT recovery_timestamp, which is set to the last checkpoint_timestamp. The problem is when the node was shut down, it took a checkpoint at the stable timestamp, which could be after the operation time that the test recorded before, so when restarting the node, the recovery_timestamp becomes greater than the operation time and caused the failure.

            Assignee:
            wenbin.zhu@mongodb.com Wenbin Zhu
            Reporter:
            wenbin.zhu@mongodb.com Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: