[IMPALA-2755] Clean up memory management in backend

• Type: Epic
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Impala 2.3.0
• Fix Version/s: Impala 2.8.0
• Component/s: Backend
• Labels: resource-management
• Target Version: Product Backlog
• Assignee: Tim Armstrong
• Reporter: Tim Armstrong
• Created: 09/Dec/15 00:18
• Updated: 16/Nov/16 16:53
• Resolved: 16/Nov/16 16:53

Description

This is an umbrella task for fixing bugs and simplifying backend code related to memory management in preparation for larger changes to how memory management is done.

Issue Links

• is a parent of: IMPALA-2354 PartitionedAggregationNode::ProcessBatch() should not continue on MEM_LIMIT_EXCEEDED
• is a parent of: IMPALA-2667 Errors in scanner prepare are not handled
• is a parent of: IMPALA-2707 Add FindOrInsert method to hash table to avoid unnecessary probe in aggregation
• is a parent of: IMPALA-1656 Remove block_mgr_client_ != NULL checks
• is a parent of: IMPALA-2757 Make RowBatch::AtCapacity checks simpler and more efficient
• is a parent of: IMPALA-2759 Use delete_on_read mode of BufferedTupleStream where appropriate
• is a parent of: IMPALA-2858 Verify that exec nodes delete blocks

Sub-Tasks

• Simplify and document invariants in Sorter: Resolved
• Don't attach BufferedTupleStreams to row batches: Resolved