Hi,   Use the below commands and see if you find any difference.   CREATE ROLE [role_name]; GRANT <PRIVILEGE> ON <OBJECT> <object_name> TO ROLE <roleName> GRANT ROLE <role_name> TO GROUP <groupName>;   Examples: create role testing; grant all on database <db-name> to role testing; grant role testing to group <group-name>;   In this case the user should be part of this particular group on all the cluster nodes - user group mapping at OS level is required. You can check the groups of a user using "id <user-name>".   Regards, Chethan YM     ... View more

Hi, Is Impala session hang means not able to run any queries? Is this issue observed via hue or impala-shell? repro the issue via impala-shell and check the coordinator logs to get any suspected error messages.  At the time of issue check the cluster load how may queries running concurrently, Issue may arise if any expensive/complex operations are running. Do not frequently run "invalidate metadata" query in the cluster it is one of the expensive operations and it pressurises the catalog service.   Regards, Chethan YM     ... View more

Hi @sukui    Can you add following --llvm_cpu_attr_whitelist  to Impala Daemon Command Line Argument Advanced Configuration Snippet (Safety Valve). --llvm_cpu_attr_whitelist=adx,aes,avx,avx2,bmi,bmi2,cmov,cx16,f16c,fma,fsgsbase,hle,invpcid,lzcnt,mmx,movbe,pclmul,popcnt,prfchw,rdrnd,rdseed,rtm,smap,sse,sse2,sse3,sse4.1,ssse3,xsave,xsaveopt   Restart impala and see if it helps.   Regards, Chethan YM ... View more

Hi,   What is the authentication mechanism given in driver? Can you change the Authentication in driver to Kerberos and provide the user kerberos credentials user and give a try?   Regards, Chethan YM ... View more

Hi,   Can you create a separate user in the database for each service and retry? You should NOT use the root user for all databases.   Refer below doc: https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ig_extrnl_pstgrs.html#cmig_topic_5_6_2   Regards, Chethan YM ... View more

Hi, > Add the below configuration in HDFS from CM UI: CM -> hdfs -> Configuration    hadoop.proxyuser.hive.hosts = * hadoop.proxyuser.hive.groups = *    > If the above is already set, please disable the DB notification API auth.  In Hive and Hive_On_Tez Service: In Hive Service Advanced Configuration hive-site safety value:    Name: hive.metastore.event.db.notification.api.auth Value: false   Restart stale configs and check if it works.   Regards, Chethan YM   ... View more

Hi,   > As per the document it is service down time, So i think it is complete impala service down time. (However I haven't seen the issue on live) > No metrics/graph to check " inc_stats_size" > If 1GB is insufficient, Try to use "compute stats" instead of  "compute incremental stats"   Regards, Chethan YM ... View more

Hi @yassan ,   I would like to let you know that, the default value on the flag(inc_stats_size_limit_bytes) is set to 200 MB, as a safety check to prevent Impala from hitting the maximum limit for the table metadata.   Whereas, the error reported usually serves as an indication that 'COMPUTE INCREMENTAL STATS' should not be used on the particular table and consider spitting the table thereby, using regular 'COMPUTE STATS'  statement if possible.    However, incase if you are not able to use the 'Compute Stats' statement then you could try to increase the default limit on the flag(inc_stats_size_limit_bytes) where, it should be set less than 1 GB limit and the value is measured in bytes.   Below is the seteps:   1. CM > Impala Service > Configuration > Search "Impala Command Line Argument Advanced Configuration Snippet (Safety Valve)" 2. Add --inc_stats_size_limit_bytes=    #####Please note that the above value is in bytes.  For example, if you want to set 400 Mb, please input 419430400(400*1024*1024). 3. Please save and restart Impala service.   Note: If I answered your question please give a thumbs up and Accept it as a solution.   Regards, Chethan YM   ... View more