Upgrading Unravel from version 4.7.x to 4.7.2.x

This topic provides instructions to upgrade from Unravel version v4.7.0.x and 4.7.1.x to 4.7.2.x.

The following upgrade paths are supported for upgrading from Unravel version v4.7.0.x and 4.7.1.x to 4.7.2.x:

4.7.0.0 → 4.7.2.x
4.7.0.1 → 4.7.2.x
4.7.1.0 → 4.7.2.x
4.7.1.1 → 4.7.2.x
4.7.2.1 → 4.7.2.x

Upgrading Unravel in a single cluster deployment (v4.7.0.x and 4.7.1.x to 4.7.2.x)

Download and extract the Unravel binaries of the Unravel version that you want to upgrade/downgrade to.
For example:
```
$ curl -v https://preview.unraveldata.com/unravel/RPM/4.7.2/unravel-4.7.2.1.tar.gz -u username:password | tar xvz -C /path/to/installation/directory
```
Note
The default installation directory is /usr/local. It may have been changed during the initial deployment. Make sure that the same installation directory is used when upgrading Unravel.

Stop Unravel.

<Unravel installation directory>/unravel/manager stop

Activate the version that you want to upgrade/downgrade to.

<Unravel installation directory>/unravel/manager activate <Unravel-version>

If an automatic Hadoop configuration has been used, run auto-configuration and refresh to automatically reload the updates.
```
<unravel_installation_directory>/unravel/manager config auto --refresh
```

Apply the changes.

<unravel_installation_directory>/unravel/manager config apply

Start all the services.

<unravel_installation_directory>/unravel/manager start

Check the status of services.
```
<unravel_installation_directory>/unravel/manager report 
```
The following service statuses are reported:
- OK: Service is up and running.
- Not Monitored: Service is not running. (Has stopped or has failed to start)
- Initializing: Services are starting up.
- Does not exist: The process unexpectedly disappeared. Restarts will be attempted 10 times.
Delete the old install directory from unravel/versions/<THE.OLD.VERSION>.

Upgrading Unravel in multi-cluster deployment (v4.7.0.x and 4.7.1.x to 4.7.2.x)

To upgrade Unravel in a multi-cluster environment, you must upgrade all the edge nodes, upgrade the core node, and pull in all the edge node updates to the core node.

Edge nodes
Run the following steps to upgrade Unravel on the edge nodes involved in Unravel monitoring.
1. Download and extract the Unravel binaries of the Unravel version that you want to upgrade/downgrade to.
  For example:
```
$ curl -v https://preview.unraveldata.com/unravel/RPM/4.7.2/unravel-4.7.2.1.tar.gz -u username:password | tar xvz -C /path/to/installation/directory
```
  Note
  The default installation directory is /usr/local. It may have been changed during the initial deployment. Make sure that the same installation directory is used when upgrading Unravel.
2. Stop Unravel.
```
<Unravel installation directory>/unravel/manager stop
```
3. Activate the version that you want to upgrade/downgrade to.
```
<Unravel installation directory>/unravel/manager activate <Unravel-version>
```
  Caution
  You may get a Network port failed precheck error if you run the manager activate command immediately after executing the manager stop command.
  To avoid this precheck error, stop Unravel and then ensure to wait for a minute or two before executing the manager activate command.
  Retry the manager activate command in case of the Network port failed precheck error.
4. If an automatic Hadoop configuration has been used, run auto-configuration and refresh to automatically reload the updates.
```
<unravel_installation_directory>/unravel/manager config auto --refresh
```
5. Apply the changes.
```
<unravel_installation_directory>/unravel/manager config apply
```
6. Start all the services.
```
<unravel_installation_directory>/unravel/manager start 
```
7. Check the status of services.
```
<unravel_installation_directory>/unravel/manager report 
```
  The following service statuses are reported:
  - OK: Service is up and running.
  - Not Monitored: Service is not running. (Has stopped or has failed to start)
  - Initializing: Services are starting up.
  - Does not exist: The process unexpectedly disappeared. Restarts will be attempted 10 times.

Core node

Run the following steps only on the core node.

Download and extract the Unravel binaries of the Unravel version that you want to upgrade/downgrade to.

Stop Unravel.

<Unravel installation directory>/unravel/manager stop

Activate the version that you want to upgrade/downgrade to.

<Unravel installation directory>/unravel/manager activate <Unravel-version>

Run auto-configuration on the core node and refresh to automatically reload the updates. Run this command only if you have run the config auto command previously on the cluster. This is an optional step.
```
<unravel_installation_directory>/unravel/manager config auto --refresh
```
Caution
If you have NOT run the manager config auto earlier on the core node, an error will be displayed, which can be ignored.
Find the edge key using the manager config edge show command and keep it handy and then run the following command for each of the configured edge node. This refreshes the configurations on the edge nodes. Provide the edge key when prompted:
```
<unravel_installation_directory>/unravel/manager config edge auto --refresh
```
For example:
```
/opt/unravel/manager config edge auto --refresh
-- Running: config edge auto --refresh
2021-09-22 03:32:25 Archiving configuration ... Ok
Edge key: edge-tnode39
```

The Hive metastore database password can be recovered automatically only for a cluster manager with an administrative account. Otherwise, it must be set manually as follows:

Run the manager config edge show command to get the <EDGE_KEY>, <HIVE_KEY>, and <CLUSTER_KEY>, which must be provided when you set the Hive metastore password.

<EDGE_KEY> is the label you provide to identify the edge node when you add the edge node in Step 3.
CLUSTER_KEY is the name of the cluster where you set the Hive configurations.
<HIVE_KEY> is the definition of the Hive service. In the output of the manager config edge show command, this is shown as the <SERVICE_KEY> for Hive.

-- Running: config edge show
------------ | ---------------------------------------- | ------------
    EDGE KEY | - edge-a                                 | Enabled
             |     Cluster manager:                     | Enabled
             |     Clusters:                            | 
 CLUSTER KEY |       - Cluster_Name                     | Enabled
             |           HBASE:                         | 
 SERVICE KEY |             - hbase                      | Enabled
             |           HDFS:                          | 
 SERVICE KEY |             - hdfs                       | Enabled
             |           HIVE:                          | 
 SERVICE KEY |             - hive                       | Enabled
 SERVICE KEY |             - hive2                      | Enabled
             |           IMPALA:                        | 
 SERVICE KEY |             - impala                     | Enabled
 SERVICE KEY |             - impala2                    | Enabled
             |           KAFKA:                         | 
 SERVICE KEY |             - kafka                      | Enabled
 SERVICE KEY |             - kafka2                     | Enabled
             |           SPARK_ON_YARN:                 | 
 SERVICE KEY |             - spark_on_yarn              | Enabled
             |           YARN:                          | 
 SERVICE KEY |             - yarn                       | Enabled
             |           ZOOKEEPER:                     | 
 SERVICE KEY |             - zookeeper                  | Enabled
------------ | ---------------------------------------- | ------------
-- OK

In a multi-cluster deployment, where edge nodes are monitoring, set the password on the core node as follows:

<Unravel installation directory>/unravel/manager config edge hive metastore password <EDGE_KEY> <CLUSTER-KEY> <HIVE-KEY> <password> 
##Example: /opt/unravel/manager config edge hive metastore password local-node cluster1 hive password

In case, the core node is monitoring the Hadoop cluster directly, run the following command from the core node.

<Unravel installation directory>/unravel/manager config hive metastore password <CLUSTER_KEY> <HIVE_KEY> <password> 
##Example: /opt/unravel/unravel/manager config edge hive metastore password cluster1 hive P@SSw0rd

Apply the changes.

<unravel_installation_directory>/unravel/manager config apply

Start all the services.

<unravel_installation_directory>/unravel/manager start

Check the status of services.

<unravel_installation_directory>/unravel/manager report

Delete the old install directory from unravel/versions/<THE.OLD.VERSION>.

Upgrading Unravel sensors

Refer to Upgrading sensors.

Important

In a multi-cluster deployment, it is mandatory to upgrade the core node before you upgrade the sensors on the edge node.

Enable Impala monitoring

After the upgrade, if you want to monitor Impala applications, you must enable the impala_worker daemon. For instructions to enable the impala_worker daemon, refer to Impala monitoring.

Enable Migration reports

If you had migrations reports on CDH or CDP clusters, you must run the following steps to continue using the migration reports.

Stop Unravel.

<Unravel installation directory>/unravel/manager stop

Enable the Migration reports as an admin user. Run the following command:

<Unravel installation directory>/unravel/manager config ondemand cloud-migration enable

Apply changes.

<Unravel installation directory>/unravel/manager apply

Start Unravel
```
<Unravel installation directory>/unravel/manager start
```
The Migration tab will be visible on the Unravel UI. Also, refer to the Migrations topics for more details.

In this section:

Home

Upgrading Unravel from version 4.7.x to 4.7.2.x

Upgrading Unravel in a single cluster deployment (v4.7.0.x and 4.7.1.x to 4.7.2.x)

Note

Upgrading Unravel in multi-cluster deployment (v4.7.0.x and 4.7.1.x to 4.7.2.x)

Note

Caution

Caution

Upgrading Unravel sensors

Important

Enable Impala monitoring

Enable Migration reports

Search results