[IMPALA-6036] Queries in admission control pool queue stay in the queue even after end client had already disconnected.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 2.13.0, Impala 3.1.0
• Component/s: Frontend
• Labels: admission-control resource-management
• Epic Color: ghx-label-3
• Assignee: Bikramjeet Vig
• Reporter: Sudarshan
• Created: 10/Oct/17 01:14
• Updated: 18/Jun/18 19:57
• Resolved: 18/Jun/18 19:56

Description

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.

Issue Links

• is part of: IMPALA-5216 Admission control queuing should be asynchronous