@Zane, The issues I can see from this profile as below: 1. The query got closed due to client inactivity: Query f64da6a899944136:22dcac6800000000 expired due to client inactivity (timeout is 10m) Not because of OOM 2. you do not have table stats, which can cause impala to use bad query plan: WARNING: The following tables are missing relevant table and/or column statistics. external_data.physician_compare This is evident that in the SUMMARY section, the estimated rows are -1: Operator #Hosts Avg Time Max Time #Rows Est. #Rows Peak Mem Est. Peak Mem Detail -------------------------------------------------------------------------------------------------------------------------- 01:EXCHANGE 1 189.890ms 189.890ms 1.02K -1 0 0 UNPARTITIONED 00:SCAN HDFS 5 98.859ms 104.753ms 22.53K -1 78.33 MB 176.00 MB external_data.physician_compare 3. Query finished in about 1 second, as result was ready after 1.45 seconds: First row fetched: 1.45s 4. I can see the query is most likely from hue: Session Type: HIVESERVER2 So my conclusion is that user stayed in Hue Hive editor idle until query is closed from server side. There is no issue from the query itself whatsoever. Cheers ... View more

@ChineduLB If you go to CM > Sentry > Configuration > search for "database", you should be able to see those database options, the one you need is "Sentry Server Database Password". Plus, you also need to make sure that the username and password you used here can connect to Sentry database. Cheers Eric ... View more

Hi Vinod, You should NOT need to restart services on weekly or monthly basis, unless you have scheduled maintenance work like making configurations changes. CDH services are expected to continue their services without the need to restart, unless you face any issues like memory pressure, crashing etc, which will require further investigation. Regarding YARN aggregation log not cleared properly, please refer to below post and KB: https://community.cloudera.com/t5/Support-Questions/Yarn-Aggregate-Log-Retention-Setting/m-p/81382 https://my.cloudera.com/knowledge/YARN-logs-under-tmp-logs-user-name-logs-not-cleared-properly?id=75330 Cheers Eric ... View more

Hi, I don't see any errors posted in the post, can you please share again? In general, Hive have locking mechanism enabled, so when INSERT is happening on a table, an exclusive lock will be place on the table and any query tries to run against the same table will have to wait, and there is a timeout to control how long the wait will be, and the query will fail with error if timeout exceeded, otherwise it will just keep waiting until lock is released. So to understand more on the issue, I need to see what error was reported. Cheers Eric ... View more

Hi, Without the actual error message, it would be quite hard to troubleshoot issues. For future reference, please share the error log if possible, it helps to determine the cause. If you want me to guess, I would think it might be caused by the fact that you create same table every time when workflow is triggered. Do you intend to overwrite the table or append data to the table? Cheers Eric ... View more