Member since
07-29-2015
535
Posts
141
Kudos Received
103
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 7900 | 12-18-2020 01:46 PM | |
| 5151 | 12-16-2020 12:11 PM | |
| 3912 | 12-07-2020 01:47 PM | |
| 2554 | 12-07-2020 09:21 AM | |
| 1657 | 10-14-2020 11:15 AM |
09-19-2018
08:30 AM
When querying a parquet hive table in impala, be sure to run: invalidate metadata <table name>; After this you should see the results.
... View more
09-10-2018
02:30 PM
@BorjaRodriguez that looks like a different known issue that we've seen with incremental stats on tables with large numbers of columns. It's fixed in CDH5.13+.
... 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
08-24-2018
12:17 AM
Thank you, I added cloudera repo to my gradle configuration and builds and functions run from Impala without problems.
... View more
07-27-2018
10:55 AM
I am seeing similar issue with ServiceMonitor and Host monitor when using Redhat 6.8 (Santiago) CM/CDH is 5.11.1 After adding JAVA_TOOL_OPTIONS=-Xss2m to hostmonitor and service monitor configuration is works fine. Is this a known issue with Redhat 6.7 as well ? (The link you mentioned is centos and its 6.9)
... View more
07-16-2018
01:37 PM
@AntonyNthanks for following up - glad to hear it!
... View more
06-23-2018
12:22 PM
Hi @rlopez, Thank you for reporting this. The 5.15.x documentations have been corrected: https://www.cloudera.com/documentation/enterprise/5-15-x/topics/impala_shell_options.html#shell_options Please continue checking back on the release notes below for when this will drop: https://www.cloudera.com/documentation/enterprise/release-notes/topics/cdh_rn_new_features.html Cheers, Vincent.
... View more
06-12-2018
05:12 PM
@mauriciothat's great news! Thanks for the update. We do need to get this documented though.
... View more
05-25-2018
05:10 AM
Hello Tim, Thank you for your help in this thread. Yes. For now, I have set the scratch limit for the specific resource pool. I set it to zero to prevent disk-to-spill and created a trigger to test whether it is working or not [IF (SELECT queries_spilled_memory_rate WHERE serviceName=$SERVICENAME AND max(queries_spilled_memory_rate) > 1) DO health:concerning]. Ideally, the trigger should not fire since the scratch limit is set to zero. For your advice.
... View more