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

Does wiredtiger.truncate satisfy the snapshot-isolation sematics?

XMLWordPrintableJSON

    • Type: Icon: Question Question
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      In oplog cleaning, mongo use session->truncate to cleanup oldest oplogs.
      Which may still be held by snapshot-manager's uncommitted_snapshots.
      If session->truncate does not satisfy snapshot-isolation, snapshot-manager's uncommitted_snapshots are not dropped but the data are deleted.
      If session->truncate does satisfy snapshot-isolation, link SERVER-29150 should be a problem?

            Assignee:
            Unassigned Unassigned
            Reporter:
            wolf_kdy deyukong
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: