Cloudera Docs

Configuring and Starting the PostgreSQL Server

By default, PostgreSQL only accepts connections on the loopback interface. Configure PostgreSQL to accept the connections based on hostname, IP address (including CIDR address), or MAC address. A fully qualified domain name (FQDN) is not a requirement. If you do not make these changes, the services cannot connect to and use the database on which they depend.

If you are making changes to an existing database, make sure to stop any services that use the database before continuing.
  1. Initialize the PostgreSQL database cluster:
    OS Command
    RHEL, SLES, and Ubuntu 
    /usr/bin/postgresql-setup initdb
  2. Make sure that LC_ALL is set to en_US.UTF-8 and initialize the database as follows:
    • RHEL
      echo 'LC_ALL="en_US.UTF-8"' >> /etc/locale.conf
    • SLES
      sudo su -l postgres -c "initdb --pgdata=/var/lib/pgsql/data --encoding=UTF-8"
    • Ubuntu
      echo ‘LC_ALL=“en_US.UTF-8”’ >> /etc/default/locale.conf
  3. Enable SCRAM-SHA-256 authentication. Edit pg_hba.conf, which is usually found in /var/lib/pgsql/data or /etc/postgresql/<version>/main. Add the following line: 
    host all all 127.0.0.1/32 scram-sha-256
    If the default pg_hba.conf file contains the following line:
    host all all 127.0.0.1/32 ident
    then the host line specifying scram-sha-256 authentication shown above must be inserted before this ident line. Failure to do so may cause an authentication error when running the scm_prepare_database.sh script. You can modify the contents of the scram-sha-256 line shown above to support different configurations. For example, if you want to access PostgreSQL from a different host, replace 127.0.0.1 with your IP address and update postgresql.conf, which is typically found in the same place as pg_hba.conf, to include:
    listen_addresses = '*'
  4. Configure settings to ensure your system performs as expected. Update these settings in the /var/lib/pgsql/data/postgresql.conf or /var/lib/postgresql/data/postgresql.conf file. Settings vary based on cluster size and resources as follows:
    • Small to mid-sized clusters - Consider the following settings as starting points. If resources are limited, consider reducing the buffer sizes and checkpoint segments further. Ongoing tuning may be required based on each host's resource utilization. For example, if the Cloudera Manager Server is running on the same host as other roles, the following values may be acceptable:
      • password_encryption = scram-sha-256
      • max_connection - In general, allow each database on a host 100 maximum connections and then add 50 extra connections. You may have to increase the system resources available to PostgreSQL, as described at Connection Settings.
      • shared_buffers - 256MB
      • wal_buffers - 8MB
      • checkpoint_segments - 16
      • checkpoint_completion_target - 0.9
    • Large clusters - Can contain up to 1000 hosts. Consider the following settings as starting points.
      • password_encryption = scram-sha-256
      • max_connection - For large clusters, each database is typically hosted on a different host. In general, allow each database on a host 100 maximum connections and then add 50 extra connections. You may have to increase the system resources available to PostgreSQL, as described at Connection Settings.
      • shared_buffers - 1024 MB. This requires that the operating system can allocate sufficient shared memory. See PostgreSQL information on Managing Kernel Resources for more information on setting kernel resources.
      • wal_buffers - 16 MB. This value is derived from the shared_buffers value. Setting wal_buffers to be approximately 3% of shared_buffers up to a maximum of approximately 16 MB is sufficient in most cases.
      • checkpoint_segments - 128. The PostgreSQL Tuning Guide recommends values between 32 and 256 for write-intensive systems, such as this one.
      • checkpoint_completion_target - 0.9.
  5. Configure the PostgreSQL server to start at boot.
    OS Command
    RHEL, SLES, and Ubuntu 
    sudo systemctl enable postgresql
  6. Restart the PostgreSQL database by running the following command:
    OS Command
    RHEL, SLES, and Ubuntu 
    sudo systemctl restart postgresql

Creating Databases for Cloudera Software

You must create databases and service accounts for components that require databases.

The following components require databases:

  • Cloudera Manager Server
  • Cloudera Management Service roles:
    • Reports Manager
  • Hue
  • Each Hive metastore
  • Oozie
  • Schema Registry
  • Streams Messaging Manager

The databases must be configured to support the PostgreSQL UTF8 character set encoding.

Record the values you enter for database names, usernames, and passwords. The Cloudera Manager installation wizard requires this information to correctly connect to these databases.

To create databases for Cloudera Manager Server, Cloudera Management Service roles, Reports Manager, Hue, Hive metastores, and Oozie, complete the following steps:

  1. Connect to PostgreSQL: 
    sudo -u postgres psql
  2. Create databases for each service you are using from the below table: 
    CREATE ROLE <user> LOGIN PASSWORD '<password>';
    CREATE DATABASE <database> OWNER <user> ENCODING 'UTF8';
    You can use any value you want for <database>, <user>, and <password>. The following examples are the default names provided in the Cloudera Manager configuration settings, but you are not required to use them:
    Table 1. Databases for Cloudera Software
    Service Database User
    Cloudera Manager Server scm scm
    Reports Manager rman rman
    Ranger RHEL/CentOS/Ubuntu ranger rangeradmin
    Ranger KMS RHEL/CentOS rangerkms rangerkms
    Hue hue hue
    Hive Metastore Server hive hive
    Oozie oozie oozie
    Schema Registry schemaregistry schemaregistry
    Streams Messaging Manager smm smm

    Record the databases, usernames, and passwords chosen because you will need them later.

  3. For PostgreSQL 8.4 and higher, set standard_conforming_strings=off for the Hive Metastore and Oozie databases: 
    ALTER DATABASE <database> SET standard_conforming_strings=off;