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

CheckReplDBHash should not fail for cases where we expect retryable findAndModify images to be inconsistent after a restart

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.2.0, 5.0.6
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • ALL
    • v5.1, v5.0
    • Repl 2021-09-20, Repl 2021-10-04, Repl 2021-10-18, Repl 2021-11-01, Replication 2021-11-15
    • 19

      A case where we expect the images in config.images_collection to be inconsistent:

      • As a secondary, we begin applying some batch (say, TS(74) -> TS(77)) with current top of oplog/last applied at TS(73)
      • We write minValid: TS(77)
      • A checkpoint happens. The stable timestamp is 73
      • We crash. We startup and do an untimestamped write to the minValid document to update the appliedThrough field.
      • The batch gets applied. isDataConsistent will evaluate to false on startup, which will cause us to mark the image as invalid.

      We should have CheckReplDBHash avoid failing in the case where both:

      • The inconsistency is in config.images_collection and it is due to images being invalidated
      • we expect server crashes/restarts in the test

            jason.chan@mongodb.com Jason Chan
            jason.chan@mongodb.com Jason Chan
            0 Vote for this issue
            4 Start watching this issue