Pre-Upgrade Steps for Impala

Complete the following steps before you upgrade Impala with or without the Installer.

Stop the Impala server, statestore, and catalog services on all Impala nodes.

Run the following command to stop the Impala server on each Impala node:

$ maprcli node services -name impalaserver -action stop -nodes <node IP addresses separated by a space>
Example:$ maprcli node services -name impalaserver -action stop -nodes 10.10.30.166

Run the following command to stop the Impala statestore instances:

$ maprcli node services -name impalastore -action stop -nodes <node IP addresses separated by a space>
Example:$ maprcli node services -name impalastore -action stop -nodes 10.10.30.166

Run the following command to stop the Impala catalog instances:

$ maprcli node services -name impalacatalog -action stop -nodes <node IP addresses separated by a space>
Example:$ maprcli node services -name impalacatalog -action stop -nodes 10.10.30.166

Preserving Impala Configuration

Starting from MEP 6.0.0, preserving of user configuration logic is built into Impala.

For a minor version update (for example, Impala-2.10-1803 to Impala-2.10-1808), user configuration from a previous version is copied to a folder with an old version timestamp and is also copied to a new version conf folder.
For a major version update (for example, Impala 2.7.0-1710 to Impala-2.10-1808), user configuration from a previous version is only copied to a folder with an old version timestamp.