[DRILL-5310] Memory leak in managed sort if OOM during sv2 allocation

• Type: Sub-task
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.10.0
• Assignee: Paul Rogers
• Reporter: Paul Rogers
• Created: 02/Mar/17 21:28
• Updated: 08/Mar/18 00:18

Description

See the "identical1" test case in DRILL-5266. Due to misconfiguration, the sort was given too little memory to make progress. An OOM error occurred when allocating an SV2.

In this scenario, the "converted" record batch is leaked.

Normally, a converted batch is added to the list of in-memory batches, then released on close(). But, in this case, the batch is only a local variable, and so leaks.

The code must release this batch in this condition.