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 Impala Incompatible Changes in the
Release Notes for any changes needed in your source code, startup scripts, and so on.

Also check Impala Known Issues in the Release Notes for any issues or limitations that
require workarounds.

Upgrading Impala through Cloudera Manager - Parcels

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

Important: 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 and choose the 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:

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

Depending on which release of Impala you are upgrading from, you might find that the symbolic links /etc/impala/conf and
/usr/lib/impala/sbin are missing. If so, see Impala Known Issues for the procedure to work around
this problem.

Restart Impala services:

Restart the Impala state store service on the desired nodes in your cluster. Expect to see a process named statestored if the service started
successfully.

If this documentation includes code, including but not limited to, code examples, Cloudera makes this available to you under the terms of the Apache License, Version 2.0, including any required
notices. A copy of the Apache License Version 2.0 can be found here.