After You Install
The following topics describe post-installation actions, such as deploying client
configuration and some simple tests to validate the installation and confirm that everything is
working as expected.
Deploying Clients Client configuration files are generated automatically by Cloudera Manager based on the services you install.Initializing Solr and creating HDFS home directory After installing the Solr service and setting up Kerberos authentication, you need to initialize the service and create the HDFS home directory. Without this, the Solr service fails to start.Testing the Installation Begin testing the installation from the Home page, where you can start by checking the health of the services.Checking Host Heartbeats One way to check whether all the Agents are running is to look at the time since their last heartbeat. You can do this by clicking the Hosts tab where you can see a list of all the hosts along with the value of their Last Heartbeat .Running a MapReduce Job Run a PiEstimator job to manually verify that the Cloudera Private Cloud Base installation was successful.Testing with Hue You can test the cluster by running Hue. Deploying Atlas service Post installation, you must plan to employ either the LDAP or Active Directory (AD) authentication mechanism to deploy the Atlas service in your production environment.Secure Your Cluster After completing your Cloudera Enterprise installation and making sure that everything is working properly, secure your cluster by enabling authentication, authorization, auditing, and encryption.Installing the GPL Extras Parcel GPL Extras contains functionality for compressing data using the LZO compression algorithm. To install the GPL Extras parcel: Configuring HDFS properties to optimize log collection CDP uses “out_webhdfs” Fluentd output plugin to write records into HDFS, in the form of log files, which are then used by different Data Services to generate diagnostic bundles. Over time, these log files can grow in size. To optimize the size of logs that are captured and stored on HDFS, you must update certain HDFS configurations in the hdfs-site.xml file using Cloudera Manager.Migrating a YARN Queue Manager database to an external database If you prefer to continue using the embedded database and do not wish to use an external database, install Cloudera Data Platform (CDP) 7.1.9 CHF 2 and disregard these instructions. See Known issues in 7.1.9 CHF 2 linked below for more information. If you want to use an external database, use PostgreSQL database, install CDP 7.1.9 or CDP 7.1.9 CHF 1, and continue with these post-installation steps to migrate your database. This migration is needed because Queue Manager uses a different database as its backing store in CDP 7.1.9 and CDP 7.1.9 CHF 2 than what was used in previous versions of CDP 7.1.8 and below. Once you have configured the database as detailed in the steps below, the data migration process is automatic.