[IMPALA-5216] Admission control queuing should be asynchronous

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 2.13.0, Impala 3.1.0
• Component/s: Backend
• Labels: admission-control resource-management
• Target Version: Product Backlog
• Epic Color: ghx-label-8
• Assignee: Bikramjeet Vig
• Reporter: Daniel Hecht
• Created: 17/Apr/17 21:16
• Updated: 19/May/20 20:26
• Resolved: 13/Jun/18 22:41

Description

Currently, admission control queuing occurs synchronously w.r.t. the ExecuteStatement client RPC. That is, a query handle is not returned until the query is admitted.

Instead, the queuing should occur on the asynchronous path. That way, the client gets a query handle back immediately and can e.g. cancel a query that is in the admission control queue.

We'll also need a way to better expose the progress of a query handle (related to IMPALA-124). E.g. that the query is queued for admission and what resource(s) it's waiting on.

Issue Links

• incorporates: IMPALA-6036 Queries in admission control pool queue stay in the queue even after end client had already disconnected.
• is depended upon by: IMPALA-6528 Enable sensible admission control limits by default
• is depended upon by: IMPALA-6969 Profile doesn't include the reason that a query couldn't be dequeued from admission controller
• is related to: IMPALA-718 ExecuteStatement (HS2) and query (beeswax) are supposed to be non-blocking RPC but for DDL, they block
• is related to: IMPALA-6248 Allow cancelling queries while starting fragments