@bigdataNico  It's a known issue with the cloudbreak deployment. Kindly refer the "Known issues: Data lake" section in the below document.   https://docs.cloudera.com/HDPDocuments/Cloudbreak/Cloudbreak-2.9.0/release-notes/content/cb_known-issues.html   Delete the "/user/hive/.yarn/package/LLAP" file, and then create a new directory in this location with the relevant permissions for the hive user. Start HiveServer2. Thanks, Prakash ... View more

@henimaher  It could be due to bug https://issues.apache.org/jira/browse/HIVE-21866    perform  yarn app -destroy llap0 and start LLAP service ... View more

https://docs.cloudera.com/HDPDocuments/Ambari-2.7.5.0/ambari-release-notes/content/known_issues.html ... View more

@AdityaShaw  Yes with the help of Yarn ACL's you can control the users submitting applications to specific yarn queue.   Kindly follow these documents to enable yarn acl.   https://docs.cloudera.com/HDPDocuments/HDP2/HDP-2.6.5/bk_yarn-resource-management/content/controlling_access_to_queues_with_acls.html   https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html ... View more

@manicool7  Can you elaborate more on the issue here and are you ingesting data from any third party like (Tableau, qlik sense) ?   Attach the error details as well ... View more

@Sham  Can you collect yarn logs -applicationId application_1594037379069_89091 > app89091.txt and attach it here.     ... View more

@Nagamalleswara  Thanks for your response, you need to open a support case with cloudera to get the patch.   Mention about the bug and the issue, your issue will be analysed and appropriate patch will be released.     ... View more

@Nagamalleswara  It's due to these bugs https://issues.apache.org/jira/browse/HIVE-22416 and https://issues.apache.org/jira/browse/HIVE-9120   You need to have a fix for these bugs to overcome this issue.   Thanks, Prakash ... View more

@TR7_BRYLE  Did we restart the agents after making the changes? can you attach the error stack trace. ... View more

@TR7_BRYLE    This issue occurs because the Java is restricting the TLSv1 from (1.8.0-171) used by the Ambari Agents. By default, ambari-agent connects to TLSv1, unless specified by force_https_protocol=PROTOCOL_TLSv1_2 in ambari-agent.ini. Hence, the Ambari- Agent is not able to connect and communicate to Ambari server.    To resolve this issue, add the following property in ambari-agent.ini [/etc/ambari-agent/conf/ambari-agent.ini] file under [security] and restart ambari-agent.   force_https_protocol=PROTOCOL_TLSv1_2   https://community.cloudera.com/t5/Support-Questions/ambari-agents-cannot-reach-ambari-server-after-changing/td-p/193251   Restart the ambari agents   Thanks, Prakash ... View more