Member since
01-15-2019
272
Posts
23
Kudos Received
29
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
687 | 01-29-2024 03:30 AM | |
1008 | 02-21-2023 05:50 AM | |
827 | 01-17-2023 05:53 AM | |
776 | 12-29-2022 03:07 AM | |
3096 | 06-28-2022 08:16 AM |
02-22-2023
02:21 AM
@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
02-21-2023
05:50 AM
@Ivoz we do not recommend to install CDP on Centos stream since this is not currently tested. I would suggest to get in touch with our professional services if you need any assistance with architecture planning and more details on roadmap. 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
02-21-2023
05:27 AM
@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
02-21-2023
05:11 AM
@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
01-17-2023
05:53 AM
@hanumanth It seems you are using other services also with embedded DB than Cloudera Manager? I see hive user also in the output. Embedded DB is only for trial poc use cases and not designed to scale. You should consider moving to external databases. https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/installation/topics/cdpdc-installing-trial-cluster.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
12-30-2022
03:45 AM
@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
12-29-2022
04:27 AM
1 Kudo
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
12-29-2022
04:03 AM
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
12-29-2022
03:50 AM
@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
12-29-2022
03:07 AM
@sathishCloudera This will only restart the stale management services. No impact to your CM server and the web UI. 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