[
https://issues.apache.org/jira/browse/IMPALA-6497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-6497.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.12.0
Impala 3.0
commit ac86e9d931fa6e5d273e51c26cd7c1d1ad2cc6ce
Author: Tim Armstrong <tarmstr...@cloudera.com>
Date: Fri Feb 9 12:00:54 2018 -0800
IMPALA-6497: add "Last row fetched" and AC events
This makes it more observable that all rows were returned to the client
and also that resources were released for admission control.
Testing:
Manually inspected some query profiles.
Added a basic observability test that ensures that the expected events
appear in the profile. Ran it in a loop for a bit to make sure it wasn't
flaky.
Change-Id: I32a707e4660061e75c86ad967f1fac6f6737da7e
Reviewed-on: http://gerrit.cloudera.org:8080/9271
Reviewed-by: Tim Armstrong <tarmstr...@cloudera.com>
Tested-by: Impala Public Jenkins
> Impala should expose when the last row is fetched
> -------------------------------------------------
>
> Key: IMPALA-6497
> URL: https://issues.apache.org/jira/browse/IMPALA-6497
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.11.0
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: admission-control, observability
> Fix For: Impala 3.0, Impala 2.12.0
>
>
> This is exposed indirectly via the "waiting to be closed" list in the Impala
> debug server. However, there is no way to tell from the profile or query
> state that the last row was fetched by the client.
> It is useful for this to be exposed to management tools since queries where
> all rows have been fetched have released resources and could be closed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
