Hi @manjj,   Thanks for reporting back the progress. There is a possible leaking somewhere in Hive even this bug was already fixed.   You can follow below steps if you do want to have the Hive Metastore canary test turned on. Steps: If Hive Metastore canary test is disabled, re-enable the Hive Metastore canary test. For configurations of both HDFS and Hive, find Service Monitor Client Config Overrides and add an entry for "fs.file.impl.disable.cache" with value "true". Restart Service Monitor And observe whether the heap also stays stable, with the canary back on. Thanks and hope this helps, Li ... View more

Hi @manjj ,   This maybe related to a known issue which we can confirm by trying below workaround:   Go to CM > Hive > Configuration Search for "Hive Metastore Canary Health Test" Uncheck the box and save the change Restart Service Monitor Please report back if above workaround actually make SMON stable and we can talk about next step.   Thanks, Li ... View more

Hi @kirill_peskov ,   Thanks for reaching out to Cloudera community and share your solution.   I was able to reproduce the issue in house and I will follow up with internal CM engineering.   Thanks! Li ... View more

Hi @manjj ,   Thanks for reaching out to Cloudera community.   Could you please share your Cloudera Manager version?   Usually the value of the SMON's heap size depends on the how many and what kind of services it monitors.  This is the public documentation which lists out the requirements: https://docs.cloudera.com/documentation/enterprise/release-notes/topics/hardware_requirements_guide.html#sizing_cm_smon__sizing_cm_smon2   To resolve the issue, you need to increase the JVM heap size. I would suggest to bump up each time with 1G. So change to 4G and see how it goes. Also make sure that the SMON host has enough free memory for any OS overhead.   Thanks and hope this helps, Li ... View more

Hi @Anil123 ,   Thanks for reaching out to Cloudera community. Could you please check a few things?   1) Make sure that selinux, ipv6, firewalls are disabled 2) Check if you have enough disk space on the cluster nodes 3) Check if the parcels are distributed in /opt/cloudera/parcels folder?   Thanks, Li   ... View more

Hi @agiese ,   Thanks for reaching out to Cloudera community!   You can follow this documentation on how to migrate from Embedded PostgreSQL Database Server to an External PostgreSQL Database: https://docs.cloudera.com/documentation/enterprise/6/6.2/topics/cm_ag_migrate_postgres_db.html   Thanks and hope this helps! Li ... View more

Hi @TR7_BRYLE ,   I am not an Ambari expert but I feel you are definitely on the right track. I wonder if you can check a couple of more things: 1. check what java version/path Ambari agent is using on the host? 2. Then compare the java.security file with the working host to confirm that it allows TLSv1.   Thanks, Li ... View more

Hi @ClouderaAdmin ,   Thanks for reaching out to Cloudera community. You should stop the cluster for doing the IP changes. See below for some recommendations which may help you: ============ Below document makes the following assumptions: Hostnames remain unchanged Nodes are not added or removed from the cluster OS or other software remain the same The entire cluster is shut down while the change is performed The process should be the same for a secure cluster, as long as name resolution works fine. Changes to be made across the cluster: Alter all hard-coded IP addresses. If /etc/hosts is used for name lookups, ensure that all hosts in the cluster are updated. If DNS is used for name lookups, allow for  TTL expiry so that the new IP addresses are returned to queries.  Zookeeper: Nothing specific to worry about if host name lookups are working correctly and quorum membership only has hostnames HDFS: Replica availability will be unaffected as the DNs will report in the new IP address when sending heartbeats Blockpool name might contain the older IP address but it's just a label and can be left alone Exclude and allow host lists should be updated, refer to dfs.hosts and dfs.hosts.exclude for file locations If racks are configured, update the topology.data file Cloudera Manager: Host to role mapping will remain valid. The agent will send in the node's new IP address in the heartbeat. Ensure that /etc/cloudera-scm-agent/config.ini on each node contains the correct hostname of Cloudera Manager node (preferred to a hard coded IP address). Note: All other services not mentioned above should continue functioning as is.   Hope this helps. Li ... View more

Hi @rar59b ,   We are sorry to hear you are having some trouble.  Can you please open a new thread and provide us with some background (environment, product you are dealing with etc) of what you are trying to do and what is happening. The original thread is talking about datanode and your question seems to refer to HMS.   Thanks! Li ... View more