Cap the size of transactions from flushing the size storer

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Execution Team 2020-08-10, Execution Team 2020-09-07, Execution Team 2020-09-21, Execution Team 2020-10-05
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      WiredTigerSizeStorer::flush() can end up creating a very large single transaction; this can be problematic for storage engines to handle.

            Assignee:
            Eric Milkie
            Reporter:
            Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: