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

background_validation_checkpoint_existence.js incorrectly assumes no checkpoint is taken between create collection and background validate cmd calls

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Storage
    • Fully Compatible
    • ALL
    • Execution Team 2020-01-13
    • 6

      The test expects here that no checkpoint will be taken between the prior create collection and background validate cmd calls. However, there is nothing preventing the mongod from taking a checkpoint: it's a race.

      I recommend converting the JS test into a unit test, where we can control whether and when checkpoints occur. We may or may not have added unit test coverage for this since the JS test was create. We should check validate_state_test.cpp and collection_validation_test.cpp to see whether we have coverage now – in which case we can just delete the JS test.

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: