Incrementally spill sorter data when using container-based spilling

XMLWordPrintableJSON

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

      Currently all of the sorted data is spilled in one burst of work, which can overwhelm the system and cause replication lag spikes that interfere with the user's foreground workload. We should instead incrementally spill the sorter data over the course of the collection scan.

            Assignee:
            Unassigned
            Reporter:
            Thomas Goyne
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: