[30/Sep/2022 19:37:38 +0000] 1048 MainThread agent WARNING Long HB processing time: 7.00362992287 [30/Sep/2022 19:38:01 +0000] 1048 DnsResolutionMonitor throttling_logger INFO DnsTest not running. Java not located. Hey @hanu Thank you for writing this in our Community. SANITY CHECKS: The above states that there could be no JAVA_HOME set. Q. Can you review if you this host has right JAVA_HOME set? or configured with a custom location? 0a. You can navigate to CM > Hosts > All Hosts> Affected Host > Quick Link > Host agent and check the value for JAVA_HOME inside the section "Component Info" 1. Make sure you have the proper values for CM agent under /etc/cloudera-scm-agent/config.ini? 1a. Compare and fix the UUID of the CM agent on the affected node, if need be. Compare CM > Hosts > All Hosts > Affected Host UUID with /var/lib/cloudera-scm-agent/uuid If they do not match, Carry on with the following steps: Navigate to CM > Hosts > All Hosts 1. Identify the UUID Click on Affected Host > Under “Details” copy the “Host ID”. This is the affected CM agent's UUID. 2. SSH to affected host, and Stop the CM agent #systemctl stop cloudera-scm-agent 3. Navigate to var/lib/cloudera-scm-agent/ 4. Make a backup of the existing uuid file. # cp var/lib/cloudera-scm-agent/uuid /tmp/agent-uuid.bk 5. Change the contents of the UUID file with the CM-UI uuid (i.e from step 1) # echo -n “<UUID_from_CM-UI>” > /var/lib/cloudera-scm-agent/uuid 6.Start the Agent: # systemctl start cloudera-scm-agent 2. Check Network configuration if there is no Heartbeat to CM Server. Try comparing and update the following as needed to match one of the nodes that does not have any issues. /etc/cloudera-scm-agent/config.ini /etc/resolv.conf /etc/hosts /etc/nsswitch.conf Once the above is updated/fixed, the CM agent requires restart: # systemctl restart cloudera-scm-agent Let us know if this helps, else, Share your observations. Thanks!
... View more
