About akhilsnaik

akhilsnaik · ‎04-12-2023

Cumulative Hotfix's are nothing but new builds with Bug fixes on top of GA version, the Upgrade procedure of Cloudera manager is same as that of GA versions, you need to follow this guide : https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/upgrade-cdp/topics/ug_cm_upgrade.html The repo's for 7.7.3CHF2 can be found on : https://docs.cloudera.com/cdp-private-cloud-base/7.1.8/manager-release-notes/topics/chf2-cm-773.html

akhilsnaik · ‎04-04-2023

Error: Could not find or load main class org.apache.ambari.metrics.AMSApplicationServer From the Error it looks like you have some issue with AMS package . have you done anything on the node recently. you can either try reinstall button in the Ambari metrics collector host component page or try command : yum reinstall ambari-metrics-collector and see if that helps.

akhilsnaik · ‎04-02-2023

so it looks like Ambari is looking for an Configuration : yarn.registry-dns.principal and its missing in Configuration. Can you see adding to yarn-env in Yarn Services configuration helps ? For ex , you can add it via commandline from Ambari serve r: /var/lib/ambari-server/resources/scripts/configs.py -l <AMBARI_HOSTNAME> -t 8080 -u <USER_NAME> -p <PASSWORD> -a set -n <CLUSTER_NAME> -c yarn-env -k 'yarn.registry-dns.principal' -v 'yarn/_HOST@EXAMPLE.COM' In the abouve example i am adding yarn/_HOST@EXAMPLE.COM as value of config : yarn.registry-dns.principal , see if this helps.

akhilsnaik · ‎11-04-2022

@abdebja , Great in that case let me know if we are good to Close the Thread , Please accept your last comment as Accept as Solution.

akhilsnaik · ‎11-03-2022

Hello @abdebja , that is strange. may i please know if you are deleting all the repos or are you keeping local repo url intact in this setting. if possible please provide your Put curl masking the cm-server, u/p and secret details so that I can reproduce the same

akhilsnaik · ‎11-02-2022

Hello @abdebja , yes its possible to remove the Default remote parcel urls via API (i assume you dont want to do the UI way which is simple and Easy ) First fetch the Configs of cloudera Manager via GET command curl -X GET "http://akhil01.novalocal:7180/api/v49/cm/config?view=summary" -H "accept: application/json" The response will have the REMOTE_PARCEL_REPO_URLS which we need to find out and correct and do a same PUT command which will update the urls . for ex : do a GET curl -X GET "http://akhil01.novalocal:7180/api/v49/cm/config?view=summary" -H "accept: application/json" { "items": [ { "name": "PROXYUSER_KNOX_HOSTS", "value": "*", "sensitive": false }, { "name": "PROXYUSER_KNOX_USERS", "value": "*", "sensitive": false }, { "name": "REMOTE_PARCEL_REPO_URLS", "value": "https://archive.cloudera.com/p/cdh7/7.1.8.0/parcels,http://cloudera-build-4-us-west-1.vpc.cloudera.com/s3/build/11800998/cfm/2.x/redhat7/yum/tars/parcel,https://archive.cloudera.com/p/cdh6/{latest_supported}/parcels/,https://archive.cloudera.com/cdh6/{latest_supported}/parcels/,https://archive.cloudera.com/p/cdh5/parcels/latest,https://archive.cloudera.com/kafka/parcels/latest/,https://archive.cloudera.com/p/cdsw1/1.10.0/parcels/,https://archive.cloudera.com/p/cfm2/2.1.4.1000/redhat7/yum/tars/parcel,https://archive.cloudera.com/p/spark3/3.3.7180.0/parcels/,http://cloudera-build-us-west-1.vpc.cloudera.com/s3/build/32427494/cdh/7.x/parcels/", "sensitive": false } ] } Now do a PUT curl -X PUT "http://akhil01.novalocal:7180/api/v49/cm/config?message=Test" -H "accept: application/json" -H "Content-Type: application/json" -d "{ \"items\": [ { \"name\": \"REMOTE_PARCEL_REPO_URLS\", \"value\": \"https://archive.cloudera.com/p/cdh7/7.1.8.0/parcels,https://archive.cloudera.com/p/cdsw1/1.10.0/parcels/,https://archive.cloudera.com/p/cfm2/2.1.4.1000/redhat7/yum/tars/parcel,https://archive.cloudera.com/p/spark3/3.3.7180.0/parcels/,http://cloudera-build-us-west-1.vpc.cloudera.com/s3/build/32427494/cdh/7.x/parcels/\", \"sensitive\": false } ]}" You can Make use of API explorer in CM which can be accessed via : http://CM-Server:port/static/apidocs/ui/index.html#/ClouderaManagerResource/updateConfig or https://archive.cloudera.com/cm-public/7.3.0-9851987/generic/jar/cm_api/apidocs/ui/index.html#/ClouderaManagerResource/getConfig to get the Exact API and more details as needed.

akhilsnaik · ‎08-23-2022

Hello @m_a_lembarki , you are in wrong place. For contact Support please refer - https://my.cloudera.com/faq/support.html Or call them at US Toll Free: 1-866-809-4659 / International: 1-650-425-9421) This is Community Forum where we discuss the issues related to Cloudera products.

akhilsnaik · ‎09-10-2019

you can give like this , if you want to use the embedded postgresql database of ambari . sudo ambari-server setup --java-home /usr/lib/jvm/java-1.8.0-openjdk/jre --enable-lzo-under-gpl-license --database=embedded reference : https://github.com/apache/ambari/blob/d44c1b118f8e17c1af83dbd71a06f1be2e82c4c3/ambari-server/src/main/python/ambari-server.py#L477 https://github.com/apache/ambari/blob/d44c1b118f8e17c1af83dbd71a06f1be2e82c4c3/ambari-server/src/main/python/ambari-server.py#L777

akhilsnaik · ‎08-18-2019

Hi @rushi_ns , yours might be completly different issue. Please create a new Question thread stating your issue.

akhilsnaik · ‎08-18-2019

Hi @khosrucse , Removal of these staging file is part of yarn application execution. But, when the yarn application itself is killed, there is not way to remove these files. The new query on top of the same table also does not have reference to these staging files(so that it can be removed by later runs), as the files are generated by Yarn application which is already killed now. For now, the only option is to manually remove the files. Though, you can refer the below link for a different approach to remove these directories. Please note, this is workaround from an end user, and thus, should be implemented with your environment in mind. https://stackoverflow.com/questions/33844381/hive-overwrite-directory-move-process-as-distcp/35583367#35583367 (for your reference )