Upgrading Impala

Each version of CDH 5 has an associated version of Impala, When you upgrade from CDH 4 to CDH 5, you get
whichever version of Impala comes with the associated level of CDH. Depending on the version of Impala
you were running on CDH 4, this could install a lower level of Impala on CDH 5. For example, if you
upgrade to CDH 5.0 from CDH 4 plus Impala 1.4, the CDH 5.0 installation comes with Impala 1.3. Always
check the associated level of Impala before upgrading to a specific version of CDH 5. Where practical,
upgrade from CDH 4 to the latest CDH 5, which also has the latest Impala.

Users running Impala on CDH 4 must upgrade to Cloudera Manager 4.8 or higher. Cloudera Manager 4.8
includes management support for the Impala catalog service, and is the
minimum Cloudera Manager version you can use.

Cloudera Manager is continually updated with configuration settings for features introduced in the
latest Impala releases.

If you are upgrading from CDH 5 beta to CDH 5.0 production, make sure you are using the appropriate CDH 5
repositories shown on the
CDH version and packaging page, then follow the procedures throughout the rest of this section.

Every time you upgrade to a new major or minor Impala release, see
Incompatible Changes in Impala
in the Release Notes for any changes needed in your source code,
startup scripts, and so on.

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:
Services > Impala > Configuration > View and Edit > Impala Daemon (Default) > Logs.
Change the setting
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.

For the resource management feature to work (in combination with CDH 5 and the YARN and Llama components),
the impala user must be a member of the
hdfs group. This setup is performed automatically during a
new install, but not when upgrading from earlier Impala releases to Impala 1.2. If you are upgrading a node
to CDH 5 that already had Impala 1.1 or 1.0 installed, manually add the
impala user to the
hdfs group.
For Llama installation instructions, see
Llama
installation.

Upgrading Impala through Cloudera Manager - Parcels

Parcels are an alternative binary distribution format available in Cloudera Manager 4.5 and higher.

Note:
In CDH 5, there is not a separate Impala parcel; Impala is part of the main CDH 5 parcel. Each level of CDH
5 has a corresponding version of Impala, and you upgrade Impala by upgrading CDH. See the
CDH 5 upgrade instructions for parcels.
The remainder of this section only covers parcel upgrades for Impala under CDH 4.

To upgrade Impala for CDH 4 in a Cloudera Managed environment, using parcels:

If you originally installed using packages and now are switching to parcels, remove all the
Impala-related packages first. You can check which packages are installed using one of the following
commands, depending on your operating system:

Use one of the following sets of commands to update Impala shell on
each node on which it is installed:

For RHEL, Oracle Linux, or CentOS systems:

$ sudo yum update impala-shell

For SUSE systems:

$ sudo zypper update impala-shell

For Debian or Ubuntu systems:

$ sudo apt-get install impala-shell

Connect to the Cloudera Manager Admin Console.

In the Services tab, click the Impala service.

Click Actions and click Start.

Upgrading Impala without Cloudera Manager

To upgrade Impala on a cluster not managed by Cloudera Manager, run these Linux commands on the appropriate
hosts in your cluster:

Stop Impala services.

Stop impalad on each Impala node in your cluster:

$ sudo service impala-server stop

Stop any instances of the state store in your cluster:

$ sudo service impala-state-store stop

Stop any instances of the catalog service in your cluster:

$ sudo service impala-catalog stop

Check if there are new recommended or required configuration settings to put into place in the
configuration files, typically under
/etc/impala/conf. See
Post-Installation Configuration for Impala
for settings related to performance and scalability.

Use one of the following sets of commands to update Impala on each
Impala node in your cluster: