Member since
08-30-2018
12
Posts
3
Kudos Received
0
Solutions
06-18-2019
03:30 PM
Thanks a lot, Tim!
... View more
03-28-2019
10:19 AM
Hi, The Impala version I'm using is 2.11, so I have those changes there. One thing I noticed is the duration, when query is submitted from impala-shell, seems to match the duration of the query reported after all rows have been fetched, but that does not seem to be the case when we actually time the duration in the client that submitted the query. As you said, probably Impala is still dealing with further processing/closing/cleanup of the query at the time the client was already able to fetch all the results of the query and print out the elapsed time. Thanks for your answer, Paulo.
... View more
01-23-2019
12:53 PM
1 Kudo
Thanks a lot! I just looked into IMPALA-7330 and I will consider upgrading Impala to 3.1.
... View more
09-06-2018
12:47 PM
1 Kudo
Untracked memory is really anything that isn't explicitly tracked by query execution. We track all of the large amounts of memory used by query execution - buffers for reading from disk, the actual row data, hash tables in joins, etc, etc. The untracked memory should be small relative to that - it's mostly overhead for control structures like the runtime profile and things like that. That's usually small but it could add up easily when there are lots of queries being left open. It looks like something is unhealthy there. For one, there are a lot of queries that are still hanging around. I'd guess that there's probably a client that is misbehaving and not closing queries once it is finished with them. Those queries look like they were probably cancelled (or had all the results fetched) but were not closed by the client. One workaround for problems like that is to set an idle session timeout to periodically clear out user sessions that are not active: https://www.cloudera.com/documentation/enterprise/latest/topics/impala_timeouts.html
... View more