Member since
10-01-2018
802
Posts
143
Kudos Received
130
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2330 | 04-15-2022 09:39 AM | |
1797 | 03-16-2022 06:22 AM | |
5258 | 03-02-2022 09:44 PM | |
2128 | 03-02-2022 08:40 PM | |
1329 | 01-05-2022 07:01 AM |
09-20-2021
05:52 AM
@SHUAIPENG I would suggest to deploy Kerberos Client Configuration once from CM > Cluster > Action menu and Also restart the CM server after that and try again to generate the credentials and see how it goes.
... View more
08-20-2021
10:32 AM
@Seedy There could be various reasons. You have to see the full agent logs. However to start with this issue I would suggest few sanity checks. 1)Resolve network issue related to firewall restrictions in accessing the repo files
2)Correct permissions on /opt/cloudera/ directories
3)Check and change the ownership.
$chown cloudera-scm:cloudera-scm /opt/cloudera/parcel-repo/*
4)Re - add the hosts from Cloudera Manager However most importantly you have to see if you can download the parcels manually on the node under this dir. Please follow the below page for detailed overview. https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ig_parcels.html
... View more
08-18-2021
01:08 AM
Yes it's available now: HDP to CDP Upgrade Overview In-place upgrade overview CDP Upgrade Readiness
... View more
08-17-2021
11:55 AM
@vishal_ That's the correct way. See deprecated items in CDP: https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/upgrade-cdh/topics/hive-unsupported.html See the recommendation for CLI in CDP: https://docs.cloudera.com/cdp-private-cloud-base/7.1.3/concepts/topics/sdx-workflow-1--using-impala-shell-and-hive.html
... View more
08-15-2021
03:35 AM
@vishal_ There may be a chance the The property "tez.history.logging.proto-base-dir" is pointing to wrong HDFS path location so check that once and correct if needed. > Then Go to CM > Tez > Actions > "Upload Tez tar file to HDFS". > Also check if hive user dir exist in hdfs else you have to go CM > Hive > Action > Create hive dir > Also, check the Hive on Tez service Environment Advanced Configuration Snippet (Safety Valve) and mention it below. AUX_CLASSPATH="$AUX_CLASSPATH:$TEZ_JARS" > Then Save changes and restart the service.
... View more
08-14-2021
08:06 PM
@zinal I would request you to check if you have root privileges on the host because that's needed for Auto-TLS. Also check the permission on the directory where CM Auto-TLS stores the certificate. Lastly you can bypass this issue by copying certs manually from below dir: Temporary directory is at: /tmp/generateHostCerts16944646874431887540 to the Auto-TLS dirs on the host and modify the config.ini file (refer the config.ini file from working host) and restart the agent.
... View more
08-14-2021
07:54 PM
@vishal_ You might be hitting this issue : https://community.cloudera.com/t5/Support-Questions/hive-server-restarted-failed-with-error-stopping-schq/td-p/312210 Please take a look and let us know if this resolves your issue.
... View more
08-14-2021
07:49 PM
@Sam2020 you are missing an important point here that is the Trial installation will always we available for latest software version. Since we have released CM7.4.4 last week so the error you are seeing is expected. You have to change you repo to https://archive.cloudera.com/cm7/7.4.4/redhat7/yum/repodata/ (try accessing this from browser you will understand). Bottom-line is if you have valid subscription you can still have 7.3.1 but if you want trial than you have to go for 7.4.4.
... View more
08-03-2021
07:54 AM
@devdb Take a look of this may be it can help : https://archive.cloudera.com/cm7/7.2.4/generic/jar/cm_api/apidocs/ Also you can get the hosts details from this : http://CM-SERVER:7180/api/v19/clusters/cluster1/services For each ‘hosts’ in http://cm:7180/api/v19/hosts iterate through the hostId … { "items" : [ { "maintenanceOwners" : [ ], "hostId" : "15b5c47f-9156-4347-abd4-efbc79d27ba2", <=== hostid "ipAddress" : "IP", "hostname" : "host", http://cm:7180/api/v19/hosts/15b5c47f-9156-4347-abd4-efbc79d27ba2. which should give you the roleName ... { "clusterName" : "Cluster 1", "serviceName" : "HDFS-1", "roleName" : "HDFS-1-DATANODE-d1ee4c53b9fbc4786263f0420c5157e8" }, { ... using the roleName http://cm:7180/api/v19/clusters/Cluster%201/services/HDFS-1/roles/HDFS-1-DATANODE-d1ee4c53b9fbc4786263f0420c5157e8 Also full deployment details http://cm:7180/api/v19/cm/deployment
... View more