Capped deletion in WT should stop using a side transaction

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The side transaction is from when we thought concurrent writes to capped collections made sense. Now that we are single-threading all capped inserts, we should make the deletion be part of the inserting transaction, as it is in MMAPv1. This will fix a lot of odd behaviors around rollback or small caps.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: