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

Background validation sees collection documents and timeseriesBucketsMayHaveMixedSchemaData at different points in time

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • ALL

      Because background validation looks back at the previous checkpoint timestamp, it sees collection documents at that time, however the timeseriesBucketsMayHaveMixedSchemaData flag now lives in the untimestamped WT table app_metadata, and as a result may be viewed further in the future.  If a user alters data in a way that is necessary to make valid a new change to this flag, background validation may for a window of time incorrectly fail this check.  This was the cause of https://jira.mongodb.org/browse/BF-34441 which is for now being resolved by applying an fsync in the failing test.

            Assignee:
            Unassigned Unassigned
            Reporter:
            binh.vo@mongodb.com Binh Vo
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: