[
https://issues.apache.org/jira/browse/IMPALA-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bikramjeet Vig resolved IMPALA-6036.
------------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
> Queries in admission control pool queue stay in the queue even after end
> client had already disconnected.
> ---------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-6036
> URL: https://issues.apache.org/jira/browse/IMPALA-6036
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Reporter: Sudarshan
> Assignee: Bikramjeet Vig
> Priority: Major
> Labels: admission-control, resource-management
> Fix For: Impala 2.13.0, Impala 3.1.0
>
> Attachments: ScreenShotSessions_ImpalaDebugWebPage.png, impala.log,
> profile_submitted_in_step_2.txt, profile_submitted_in_step_3.txt
>
>
> Steps to reproduce :-
> ------------------------------
> 1) Set Impala admission control queue concurrency to 1.
> 2) Submitting a long running query. Anything submitted after this query will
> be queued.
> 3) Submit another query. This query will get queued due to admission control
> queue concurrency of 1.
> 4) Disconnect the client that submitted the query in step 3, above.
> Expected observation :-
> ------------------------------
> Ideally you would want that the query submitted in step 3 to get canceled as
> soon as the client disconnects.
> What happens :-
> ------------------------
> Query submitted in step 3 stays in the queue until it gets a chance to
> execute. This causes the coordinator to start the fragments and then realize
> that the client had already disconnected.
> Attachments :-
> ------------------------
> 1. impala.log
> 2. profile_submitted_in_step_2.txt ==> query profile
> 3. profile_submitted_in_step_3.txt ==> query profile
> 4. ScreenShotSessions_ImpalaDebugWebPage.png ==> Screen shot of sessions as
> seen from Impala debug web page.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
