Cloudera Community
h2rr821
user rank
Explorer
My Accepted Solutions
Show All

Re: How to upgrade the cloudera runtime with cloud...

by Explorer in Support Questions
‎08-09-2023 02:59 PM
‎08-09-2023 02:59 PM
yes. it is working. thank you!! ... View more

How to upgrade the cloudera runtime with cloudera ...

by Explorer in Support Questions
‎08-08-2023 03:58 PM
‎08-08-2023 03:58 PM
I am new to cloudera rest api. I try to upgrade the cloudera runtime with rest api instead of the web-ui for automation.    I am able to download the CDH with rest api.    curl -X POST -u admin:admin "http://{url}:7180/api/v44/clusters/{cluster-name}/parcels/products/CDH/versions/7.1.8-1.cdh7.1.8.p0.30990532/commands/startDownload"   I am stuck on it ask for upgrade the cluster when it finish the download. From the Web-UI.  it is a series of process.       I can skip all the checkup step(I understand the risks) and upgrade the cluster.   How to do that with the rest api? Thank you very much!!   ... View more

Re: How to upgrade the postgresql jdbc driver

by Explorer in Support Questions
‎08-01-2023 09:17 AM
‎08-01-2023 09:17 AM
1. Identify compatible version 2. Backup of the existing Cloudera PostgreSQL JDBC driver files(postgresql-42.3.2.jar,postgresql-42.3.3.jar, postgresql-42.2.16.jar) 3. Download the new PostgreSQL JDBC driver files(postgresql-42.6.0.jar, postgresql-42.2.27.jre7.jar, and postgresql-42.3.8.jar). 4. Stop Cloudera services using the Web-UI and command(I do not understand how to Stop Cloudera services using the PostgreSQL JDBC driver)  5. Replace old JAR files:  /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.2.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.3.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.2.16.jar with the new ones /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.6.0.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.8.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.2.27.jre7.jar 6. Ensure new JAR files have correct permissions. 7. Start services: Restart Cloudera services. Then the schema registry server will has problem. It do run for a while, and it fail. I cannot successfully restart the schema registry server without put back the old jar file to the folder(/opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/) ... View more

Re: How to upgrade the postgresql jdbc driver

by Explorer in Support Questions
‎07-31-2023 02:18 PM
‎07-31-2023 02:18 PM
I try to replace it with the latest jdbc jar file(postgresql-42.2.27.jre7.jar and postgresql-42.3.8.jar). then the schema registry server will has problem.      ... View more

How to upgrade the postgresql jdbc driver

by Explorer in Support Questions
‎07-27-2023 01:09 PM
‎07-27-2023 01:09 PM
I am using redhat 7.9 OS, and CM 7.7.1. base on the  CVE-2022-41946 security issue, https://www.postgresql.org/about/news/postgresql-jdbc-4251-4243-4238-42227jre7-security-update-for-cve-2022-41946-2551/ I need to upgrade the cloudera postgresql jdbc driver files   I saw the jdbc driver file is the following for the CDH-7.1.8.: /opt/cloudera/cm/common_jars/postgresql-42.2.14.jre7.6ce27816399941030df9ad06f89fa77b.jar /opt/cloudera/cm/common_jars/postgresql-42.2.24.jre7.a7b0f155b668470fb4e212e79724cc7d.jar   /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.2.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.3.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.2.16.jar   I think just do a replacement for those jar files is a risk.   How can I upgrade those file to PostgreSQL JDBC Driver version 42.2.27, 42.3.8, 42.4.3, 42.5.1, or later.   Thank you!! ... View more

Re: in-place upgrade CM problem(CM 7.4.4 to CM 7.7...

by Explorer in Support Questions
‎07-27-2023 08:07 AM
1 Kudo
‎07-27-2023 08:07 AM
1 Kudo
After I change to monitored_nodev_filesystem_types=tmpfs in /etc/cloudera-scm-agent/config.ini, it solve my problem.  ... View more

in-place upgrade CM problem(CM 7.4.4 to CM 7.7.1)

by Explorer in Support Questions
‎07-26-2023 08:38 AM
‎07-26-2023 08:38 AM
Redhat 7 OS. I try to do a in-place upgrade Cloudera Manager from 7.4.4 to 7.7.1 following the docs:   https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/upgrade-cdp/topics/ug_cm_upgrade_after-cdp.html   I do anything, and after the upgrade, I found the cloudera-scm-agent is not stable.   the cloudera-scm-agent log is:   [26/Jul/2023 15:11:31 +0000] 1956 MainThread filesystem_map ERROR NFS server binding info failed with error :- rpcinfo: RPC: Port mapper failure - Timed out program 100003 is not available [26/Jul/2023 15:12:31 +0000] 1956 MainThread filesystem_map ERROR NFS server binding info failed with error :- rpcinfo: RPC: Port mapper failure - Timed out program 100003 is not available [26/Jul/2023 15:13:31 +0000] 1956 MainThread filesystem_map ERROR NFS server binding info failed with error :- rpcinfo: RPC: Port mapper failure - Timed out program 100003 is not available [26/Jul/2023 15:14:31 +0000] 1956 MainThread filesystem_map ERROR NFS server binding info failed with error :- rpcinfo: RPC: Port mapper failure - Timed out program 100003 is not available [26/Jul/2023 15:15:31 +0000] 1956 MainThread filesystem_map ERROR NFS server binding info failed with error :- rpcinfo: RPC: Port mapper failure - Timed out program 100003 is not available [26/Jul/2023 15:16:31 +0000] 1956 MainThread filesystem_map ERROR NFS server binding info failed with error :- rpcinfo: RPC: Port mapper failure - Timed out program 100003 is not available [26/Jul/2023 15:16:32 +0000] 1956 MainThread agent ERROR Heartbeating to mysiteaddress.com:7182 failed.   Any suggestions? Thank you!! ... View more
Contact Me
Online
Offline
Last Visited
‎10-23-2023 12:30 PM
Community Statistics
Member Since ‎07-26-2023 08:21 AM
Last Visited ‎10-23-2023 12:30 PM
Posts 7
Kudos received 1