Installing Impala with Cloudera Manager
Before installing Impala through the Cloudera Manager interface, make sure all applicable nodes have the appropriate hardware configuration and levels of operating system and CDH. See Cloudera Impala Requirements for details.
To install Impala version 1.2.1, upgrade Cloudera Manager to 4.8 or higher. Cloudera Manager 4.8 is the first release that can manage the Impala catalog service introduced in Impala 1.2. Cloudera Manager 4.8 requires this service to be present, so if you upgrade to Cloudera Manager 4.8, also upgrade Impala to 1.2.1 at the same time.
For information on installing Impala in a Cloudera Manager-managed environment, see the Cloudera Manager Installation Guide.
Managing your Impala installation through Cloudera Manager has a number of advantages. For example, when you make configuration changes to CDH components using Cloudera Manager, it automatically applies changes to the copies of configuration files, such as hive-site.xml, that Impala keeps under /etc/impala/conf. It also sets up the Hive metastore service that is required for Impala running under CDH 4.1.
In some cases, depending on the level of Impala, CDH, and Cloudera Manager, you might need to add particular component configuration details in one of the "Safety Valve" fields on the Impala configuration pages within Cloudera Manager.
Due to a change to the implementation of logging in Impala 1.1.1 and higher, currently you should change the default setting for the logbuflevel property for the Impala service after installing through Cloudera Manager. In Cloudera Manager, go to the log settings page for the Impala service: Impala Daemon Log Buffer Level (logbuflevel) from -1 to 0. You might change this setting to a value higher than 0, if you prefer to reduce the I/O overhead for logging, at the expense of possibly losing some lower-priority log messages in the event of a crash.. Change the setting
|<< Previous: Cloudera Impala Requirements||Next: Installing Impala without Cloudera Manager >>|