Pre-Upgrade Steps for Impala
Complete the following steps before you upgrade Impala with or without the MapR Installer.
About this task
IMPORTANT This component is deprecated. Hewlett Packard
Enterprise recommends using an alternate product. For more information, see Discontinued Ecosystem Components.
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 EEP 6.0.0, preserving of user configuration logic is built into Impala.
Procedure
-
For a minor version update (for example,
Impala-2.10-1803
toImpala-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 versionconf
folder. -
For a major version update (for example,
Impala 2.7.0-1710
toImpala-2.10-1808
), user configuration from a previous version is only copied to a folder with an old version timestamp.