@Praty you should already be on this base version. Check all available versions here https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/release-guide/topics/cdpdc-runtime-download-information.html   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.   ... View more

@Praty you can directly upgrade from CDP 7.1.7 to sp2. Refer Table 2 in the below document which mentions the supported upgrade paths. https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/upgrade/topics/cdppvc-upgrade-paths.html Please take note that currently sp2 is only supported with CM 7.6.7 Refer- https://supportmatrix.cloudera.com/   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.       ... View more

@allenchen check if the parcels and sha files exist on CM server under /opt/cloudera/parcel-repo [default location] and files permission should be owned and accessible by cloudera-scm user. Make sure agents are able to heartbeat correctly to CM server, try restarting the CM agent and check the CM agent logs , flood logs etc to look for any parcel errors. Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.   ... View more

@sanjaysubs glad to know manual install worked. The fact that install was successful in CM node, means there was probably issue with missing allkeys.asc. This file should be present in the repository that you configure in the add host wizard on CM UI. This is required by the install wizard in the nodeconfigurator process for installation of other CM agent nodes. ... View more

This issue would be fixed in our upcoming release. You can check for a hotfix.   You can try adding the below workaround as well to see if performance improves. a. On the target cluster, Go to CM-> Hive-> Configuration b. Add "HIVE_REPL_STATS_ENGINE=hive" to the "Hive Replication Environment Advanced Configuration Snippet (Safety Valve)" configuration .   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

you should check the container logs for the one mentioned in the snapshots above for more details. Generally caused due to resource crunch. You can consider increasing the below yarn configs as well. yarn.nodemanager.resource.memory-mb yarn.nodemanager.resource.cpu-vcores   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@frank_albers @PNW supervisor has a listener process which keeps monitoring the CDH processes. For any service with auto restart configured if faces an unexpected exit , supervisord will restart the process. Agent looks for unexpected exits in the notifications it receives via the supervisor listener and forwards relevant event info to the associated role's monitor to update its unexpected exit state. A normal agent restart does not affect supervisord process, it continues to be running and managing CDH processes. A hard stop/restart on agent will affect supervisord and in turn kill all managed CDH processes.   Hope this helps, Paras Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.     ... View more