Member since
03-23-2015
1288
Posts
114
Kudos Received
98
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4332 | 06-11-2020 02:45 PM | |
5937 | 05-01-2020 12:23 AM | |
3766 | 04-21-2020 03:38 PM | |
4039 | 04-14-2020 12:26 AM | |
2987 | 02-27-2020 05:51 PM |
08-11-2019
04:42 PM
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
08-09-2019
07:09 PM
1 Kudo
Hi, "HiveServer2 Enable Impersonation is setting to TRUE" is probably the reason. When Impersonation is true, it means Hive will impersonate as the end user who runs the query to submit jobs. Your ACL output showed that the directory is owned by "hive:hive" and as @Tomas79 found out, you have sticky bit set, so if hive needs to impersonate as the end user, the end user who runs the query will not be able to delete the path as he/she is not the owner. If impersonation is OFF, then HS2 will run query as "hive" user (the user that runs HS2 process), then you should not see such issue. I assume you have no sentry? As sentry will require Impersonation to be OFF on HS2 side, so that all queries will be running under "hive" user. To test the theory, try to remove the sticky bit on this path and drop again in Hive. Cheers Eric
... View more
08-09-2019
02:38 AM
Thanks a lot. I removed the create hive table statement.The job is successfully executed now.
... View more
08-06-2019
10:55 AM
I'm happy to see you resolved your issue. Please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
08-04-2019
08:54 PM
1 Kudo
Thanks you. Yes, It is not problem of UDF. I have 2 HiveServer2 server host. I have been register udf only 1 server host. Maybe. It is reason.
... View more
07-29-2019
05:12 PM
I filed https://issues.apache.org/jira/browse/IMPALA-8807 to fix the docs.
... View more
07-26-2019
10:26 AM
Like @EricL said, this would be caused by some process updating files in the table in the background without a refresh in Impala. E.g. if you have a job that writes files directly into the table and can either write incomplete files or has Impala see the files before they are completely written (preferably you write the files in a temporary directory then move them into the table directory). Some usage patterns for hive might cause issues, e.g. INSERT OVERWRITE. There was a related issue in Impala that could occur if you did an "INSERT OVERWRITE" from hive without a refresh from Impala: https://issues.apache.org/jira/browse/IMPALA-8561. Generally that workflow (insert overwrite without refresh) is problematic, but the symptoms were made more confusing by IMPALA-8561.
... View more
07-26-2019
07:25 AM
Hi were we able to get to the root cause of this issue? Are you getting any error in log?
... View more