Hi @manojamr    Step 1: Could you run the following commands to gather column statistics for all the table that is involved in the query. analyze table <TABLE-NAME> compute statistics; analyze table <TABLE-NAME> compute statistics for columns; Reference: https://cwiki.apache.org/confluence/display/Hive/StatsDev   Step 2: set the following property in session level set hive.tez.container.size=10240 ; set hive.tez.java.opts=-Xmx8192m; set tez.runtime.io.sort.mb=4096; set tez.task.resource.memory.mb=7680; set tez.am.resource.memory.mb=10240; set tez.am.launch.cmd-opts=-Xmx8192m;   If Step2 got succes ignore step 3.   Step 3: Re-run the job at the beeline session-level. If the job fails again, I would request the below details. 1. Complete query, 2. Beeline console output, 3. QueryId of the job 4. HS2 and HMS logs and 5. Application logs. ... View more

Hi @saikat  As I can understand you are running a merge query and it is failing with java.lang.OutOfMemoryError error.   Step 1: Could you please run major compaction on all the tables involves in the merge query(If it is an ACID table or else ignore step1). Once the major compaction is triggered make sure it got completed by running "show compactions;" command in the beeline. This will bring down some stats collection burden for the hive. How to run minor and major compaction? Alter table <table name> compact 'MAJOR'; Step 2: Once step1 is done. Please set the following propery in beeline session level and re-run the merge query set hive.tez.container.size=16384; set hive.tez.java.opts=-Xmx13107m; set tez.runtime.io.sort.mb=4096; set tez.task.resource.memory.mb=16384; set tez.am.resource.memory.mb=16384; set tez.am.launch.cmd-opts=-Xmx13107m; set hive.auto.convert.join=false; The TEZ container and AM size is set as 16GB, if the query got failed you can increase the value to 20GB(then hive.tez.java.opts and tez.am.launch.cmd-opts need to be configured 80% of container and AM size that is 16384). If the query got succeeded with 16GB of TEZ container and AM size then you can try to decrease it too 14/12/10 and figure out a benchmark where it is failing and getting succeeded. In this way, you can save resources. If you are happy with the comment, Mark it "Accept as Solution". ... View more

If I installed a later version of Zookeeper (for example), would ambari recognize that later version in it's management? Or would it exist in parallel with the version of Zookeeper packaged with 3.1.5?   > You have to install zookeeper or any component via Ambari only, if you install it manually(via yum or apt) in the server ambari will not recognize or it will not consider it.   Grafana is running v6.4.2, but has a major security issue that was patched in future releases: https://grafana.com/blog/2020/06/03/grafana-6.7.4-and-7.0.2-released-with-important-security-fix/ Infra Solr is running SOLR 7.7 and has an RCE vulnerability. This was patched in SOLR 8.3, which is not part of Ambari 2.7.5's InfraSolr. Zookeeper packaged is 3.4.6, but SSL implementation was added in 3.5.5   > As mentioned already please create a support case with Cloudera along with the vulnerability CVE number so we can check with our team and confirm whether our product is vulnerable to the security concern or not. If it is so we can provide a patch to overcome it.   If you are happy with the comment, Mark it "Accept as Solution". ... View more

Hi @Nil_kharat    Generally, in Hive you may see Query slowness, Query failure, Configuration issue, Alerts, Services down, Vulnerability issue, some bugs this kind of issues you may see.   ... View more