• Type: Task
    • Resolution: Unresolved
    • Priority: High
    • None
    • Affects Version/s: None
    • Component/s: None
    • 2
    • Tools and Replicator
    • 1

      Because the oplog can contain changes from a timesamp from before the timestamp for a document restored from the data dump, it's possible for updates in the oplog to cause a document to violate constraints. We saw this with timeseries collections, where the Server always checks these constraints in newer versions. This was covered in TOOLS-4373 and the accompany IA doc - https://docs.google.com/document/d/1rsftcjCaQ6LQmyiGcSlSuWzecg1iPcDNMWL6fTMKe80/edit?tab=t.0

      Once we finish applying the oplog, we expect all documents to be in a valid state, because the oplog will include ops for a timestamp that is greater than or equal to the timestamp of the data in the data files.

      Based on this, we realized that we should always disable validation constraints during oplog application. If we don't, we will abort mid-restore with a confusing error, even though we could safely finish the restore.

            Assignee:
            Unassigned
            Reporter:
            Dave Rolsky
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: