Changing the CM database is a little annoying, but very possible. Here's
the steps, which involve cluster downtime:
1) Stop everything through CM UI
2) save to a file the JSON from http://
3) stop CM (sudo service cloudera-scm-server stop)
4) stop all CM agents on all hosts in your cluster (sudo service
5) back up and then edit /etc/cloudera-scm-server/db.properties to point to
your new mysql, empty schema
6) start CM (sudo service cloudera-scm-server start)
7) log in to CM as admin/admin. It will think it is brand new (since it's
on a new db)
8) HTML PUT the data from step 2 to the same url,http://<host>:7180/api/v4/cm/deployment?view=export.
You can use curl or a browser plugin like POSTMAN to do this.
8a) You should see all of your cluster configuration re-appear, and all of
your hosts should be present
9) start all CM agents on all hosts in your cluster (sudo service
10) start the cluster and management service in the CM UI
11) When you are satisfied everything is working, stop the embedded db
(sudo service cloudera-scm-server-db stop)
If anything goes wrong, your CM configuration data is still in the embedded
postgresql and you can easily revert by replacing db.properties with the
backup you took in step 5.
On Thu, Nov 7, 2013 at 8:14 AM, wrote:
I have installed cloudera manager using automatic install option. I
realized that I have missed setting up the MySQL database for cloudera
manger (configurations/commands etc). Is there a way to re-configure
cloudera manager to use MySQL and NOT embedded Postgresql?
I was able to change to databases for
Activity/Host/ReportsManager/EventServer/AlertPub/ServiceMonitor to MySQL.
I am using CM 4.6.3.
Thanks in advance.
To unsubscribe from this group and stop receiving emails from it, send an
email to firstname.lastname@example.org.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.