What Databases Must Be Installed
The Cloudera Manager Server and the server's Activity Monitor, Service Monitor, Report Manager, and Host Monitor all require databases, as does Cloudera Navigator and the Hive Metastore. Cloudera Manager does support deploying different types of databases in a single environment, but doing so may create unexpected complications. Cloudera recommends choosing one of the three database providers to use for all of the Cloudera Manager databases.
Cloudera provides two install paths:
- Path A automatically installs embedded PostgreSQL databases to meet the requirements of the services. This path reduces the number of installation tasks you must complete, as well as the number of choices to make.
- Path B requires you have databases in your environment for use by Cloudera Manager, Cloudera Management Services, and Hive metastore. This path requires more input and intervention as you either install databases or gather information about existing databases. This path also provides greater flexibility in choosing database types and configurations.
A service works with a database. In most cases, you should install databases and services on the same host. For example, if you create the database for Activity Monitor on myhost1, then you should typically assign the Activity Monitor role to myhost1. You will assign the Service Monitor, Activity Monitor, Report Manager, and Host Monitor roles in the Cloudera Manager wizard during the install or upgrade process. After completing the install or upgrade process, you can also modify role assignments in the Management services pages of Cloudera Manager. While it is true that database location is changeable, before beginning an installation or upgrade, you should decide which hosts you will use. Note that the JDBC connector for your database must be installed on the hosts where you assign the Service Monitor, Activity Monitor, Report Manager, and Host Monitor roles. Installing JDBC connectors is described later in this guide.
It is possible to install the database and services on different hosts. Separating databases from services is more likely to occur in larger deployments and in cases where more sophisticated database administrators actively choose to establish such a configuration. For example, databases and services might be separated if your environment includes Oracle databases that will be separately managed by Oracle database administrators (DBAs).
The table that follows provides a summary; details are in the sections that follow.
Install or Upgrade Path |
Install Supported Database For |
Typically Install Databases on Systems That Will Host |
---|---|---|
Installation Path A - Automated Installation by Cloudera Manager |
No installations required. Automated installation automatically creates embedded PostgreSQL databases for all Cloudera Manager and all services. |
No manual installation required. |
The Cloudera Manager Server configuration and for Activity Monitor, Service Monitor, Report Manager, Host Monitor, Hive Metastore, and Cloudera Navigator. |
The Cloudera Manager Server, Activity Monitor, Service Monitor, Report Manager, Host Monitor, and Cloudera Navigator roles, and the Hive Metastore. Alternately, you may install these databases on other systems, assuming those systems are accessible to the Cloudera Manager Server. |
|
Host Monitor and Cloudera Navigator roles, and the Hive Metastore. |
Host Monitor and Cloudera Navigator roles, and the Hive Metastore. |