You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/06/13 22:42:00 UTC
[jira] [Resolved] (IMPALA-5216) Admission control queuing should be
asynchronous
[ https://issues.apache.org/jira/browse/IMPALA-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-5216.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
Resolving on Bikram's behalf - he's afk for a bit.
> Admission control queuing should be asynchronous
> ------------------------------------------------
>
> Key: IMPALA-5216
> URL: https://issues.apache.org/jira/browse/IMPALA-5216
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Reporter: Dan Hecht
> Assignee: Bikramjeet Vig
> Priority: Major
> Labels: admission-control, resource-management
> Fix For: Impala 2.13.0, Impala 3.1.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org