Member since
10-01-2018
802
Posts
143
Kudos Received
130
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 3072 | 04-15-2022 09:39 AM | |
| 2475 | 03-16-2022 06:22 AM | |
| 6554 | 03-02-2022 09:44 PM | |
| 2907 | 03-02-2022 08:40 PM | |
| 1915 | 01-05-2022 07:01 AM |
01-28-2021
11:46 AM
@Alex_IT All you need is a backup of the CM DB and then you have to create the CM DB on Oracle 19c and dump the old backup there. Then you have to point the db.properties file to the new DB server. This doc can give you a high level steps with respect to DB migration but at core the objective is same. https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ag_migrate_postgres_db_to_oracle_mysql.html
... View more
01-27-2021
05:16 AM
@Magudeswaran Interesting can you open this in some other browser and also check the console logs in web developer tool and what it says.
... View more
01-27-2021
12:07 AM
@Magudeswaran There might be an issue with bind user password try resetting that. What Ambari version you are using?
... View more
01-25-2021
03:55 AM
@NegativeNathan There might be some issue with Auto-TLS where the deployment interrupted and you are getting this error. I would suggest you to check if Auto-TLS is enabled successfully and then restart CM server again and then restart management services to get Auto-TLS in effect.
... View more
01-25-2021
03:52 AM
@Sreenath I think this is because of the https://issues.apache.org/jira/browse/HIVE-23408 where the secure connection is not available yet.
... View more
01-25-2021
03:46 AM
@sharathkumar13 The error indicates that your hosts are not heartbeating to Cloudera Manager hence you are not able to start mgmt service. Please check the config.ini file and see if the CM server hosts name is correct and also check if agent is running on the host.
... View more
01-25-2021
02:52 AM
@avengers This is Resident memory used you can check the doc here: https://docs.cloudera.com/documentation/enterprise/5-8-x/topics/cm_metrics_monitor.html
... View more
01-25-2021
02:33 AM
@analytics-shek I guess you have the packages available already hence you can add service but if you want to build cluster from scratch then you will not be able to do that.
... View more
01-25-2021
02:30 AM
@mike_bronson7 Looks like your question is covered here: https://community.cloudera.com/t5/Support-Questions/hadoop-cluster-with-active-standby-namenode-gap-in-the-edit/m-p/310047/highlight/false#M224002
... View more
01-25-2021
02:29 AM
1 Kudo
@mike_bronson7 There is a solution which can help. Run the following command on the Standby NameNode: # su hdfs -l -c 'hdfs namenode -recover' Following message can be seen: You have selected Metadata Recovery mode. Thismode is intended to recover lost metadata on a corrupt filesystem. Metadata recovery mode often permanently deletes data from your HDFS filesystem. Please back up your edit log and fsimage before trying this! Are you ready to proceed? (Y/N) (Y or N) To proceed further, select option "yes", the recovery process will read as much of the edit log as possible. When there is an error or an ambiguity, it will prompt how to proceed. There will be further options prompted as Continue, Stop, Quit, and Always. Mostly the data loss ( due to transaction skip/miss ) is possible when using this method. This method is therefore not to be used, if data/transaction losses has to be avoided.
... View more