[IMPALA-4836] Kudu scans should operate within a memory constraint

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: Impala 2.9.0
• Component/s: Backend
• Labels: kudu resource-management
• Epic Link: Operator memory constraints
• Target Version: Product Backlog
• Assignee: Unassigned
• Reporter: Tim Armstrong
• Created: 27/Jan/17 22:56
• Updated: 02/Oct/18 00:55

Description

It is somewhat unclear how we will do this, given that Kudu does its own memory management outside of our buffer pool.

Issue Links

• relates to: IMPALA-7096 Ensure no memory limit exceeded regressions from IMPALA-4835 because of non-reserved memory