[IMPALA-470] Impala needs to cancel queries that are "inactive" after some timeout period.

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 1.0
• Fix Version/s: Impala 1.2.1
• Assignee: Henry Robinson
• Reporter: Nong Li
• Created: 18/Jul/13 20:32
• Updated: 18/Nov/13 01:19
• Resolved: 18/Nov/13 01:19

Description

Currently, if a query is run and the client does not call FetchNextBatch, the query would run forever. This
is a resource "leak". You could imagine a client with a UI that reads a batch of results and then has to hit
'next' to get the next batch.

I think we should timeout a query after sometime of client inactivity. This is also a catch all for client side
issues.