About the Cloudera Manager Server Database

This database, which is used for storing information about services' configurations, is independent of the databases used by the Activity Monitor, Service Monitor, Report Manager, Host Monitor, Cloudera Navigator, or the Hive Metastore.

Installation type

Process

Automatic installation: Installation Path A

The wizard automatically installs, configures, and uses embedded PostgreSQL databases to store information about service configuration, as well as the Activity Monitor, Service Monitor, Report Manager, Host Monitor, Cloudera Navigator, and the Hive Metastore. This functionality is provided by the cloudera-scm-server-db package, and you can start and stop these databases using the service cloudera-scm-server-db [start|stop] command. If you are using Installation Path A, you can proceed directly to Installation Path A.

Manual installation: Installation Path B

You must install a supported database. This database can be installed on the machine where you install the Cloudera Manager Server or on a machine accessible to the Cloudera Manager Server. You will need to configure the connection between Cloudera Manager and the database, as is described in the documentation for Path B.

The installation instructions for the database containing the Cloudera Manager Server's configuration are also included under Installation Path B - Installation Using Your Own Method.

  Important:
  • To prevent deadlocks, Cloudera Manager requires the isolation level to be set to read committed. This is the default setting for PostgreSQL and Oracle. The instructions for using a MySQL database with Cloudera Manager describe how to configure this setting. Contact your DBA to find out what your isolation level currently is set to.
  • If you use a MySQL database to store information about service configuration, make sure that the InnoDB engine is configured, not the MyISAM engine. Cloudera Manager will not start if its tables are configured with the MyISAM engine. (Typically, tables revert to MyISAM if the InnoDB engine is misconfigured.) To check what engine your tables are using, run the following command from the MySQL shell:
    mysql> show table status;