Try The below solutions.  @myzard Can you compare the values of hive.heapsize on this cluster that seem to be the issue? Please adjust them depending on the memory the HiveServer2 Heap Size automatically shows you the memory available to the cluster so i.e on my 24 GB single node I dedicated 8 GB for hive.heapsize and it fires up! Possible SLotion: 1. Increase the llap queue resource percentage 2. Try restarting YARN service and then restarted HS2I   ... View more

Yes to allow anonymos user you can define {USER} in ranger nifi policy and you will not see these deny operation.  ... View more

You can try below.    -increasing the heap size of this HiveServer2 role by changing the field Hive - Configuration - 'Java Heap Size of HiveServer2 in Bytes' to 24 GiB for this role instance. - Increasing the time out for the hive service To check further provide   From the SERVICEMONITOR system, please do the following: cd /var/log/cloudera-scm-firehose gzip -c *SERVICEMONITOR*.out > sm.out.gz     ... View more

@SchmidtS  If In case you are not currently using the latest version of the Impala ODBC driver, please update the driver to the latest version (2.6.16 currently). Please note that 2.6.16 supports CDH6 so there should not be any incompatibility. You can download the latest version of Impala ODBC driver in the below link: https://www.cloudera.com/downloads/connectors/impala/odbc/2-6-16.html ... View more

The following areas normally cause this problem: 1) the connection from Ambari agent host to Ambari Server got lost. 2) firewall issue blocked connections. 3) hostname and IP address are not being set correctly in /etc/hosts   You can compare the output using these APIs: > curl ­u user:passwd http://AmbariHost:8080/api/v1/hosts ... View more