Upgrading Jethro

The procedures for upgrading Jethro differ depending on the version of Jethro that you are upgrading from.

It is recommended to follow the upgrade instruction of every release, starting from the version you are upgrading from, until the one you are upgrading to.

For a smooth upgrade, be sure to first also review the important version-specific information found in the release notes, for every version relevant for your upgrade process, as it could have an impact on Jethro's functionality and performance.

Table of contents

General Upgrade Procedure

To upgrade Jethro Server, apply the following steps on each Jethro query node machine:

Read the version specific upgrade notes which are relevant for your upgrade process, and perform all the steps which are required to be made, before starting the upgrade process.
Sign in as the user admin for jethro (usually 'jethro')
Stop all the services of Jethro's instances, by running:
```
service jethro stop
```
Sign in as user root.
Download the latest RPM of Jethro.
Run the command:
```
RPM -Uvh <jethro-rpm>
```
For example:
rpm -Uvh latest-rpm
Stop all the services of Jethro's instances, by running:
```
service jethro start
```
Read again, the version specific upgrade notes which are relevant for your upgrade process, and perform all the steps which are required to be made, after finishing the upgrade process.

Version Specific Upgrade Notes

Jethro 3.4.2

After upgrade to 3.4.2, and only for users who are using Kerberos, it is highly recommended to configure the Kerberos ticket renewal process using the new monitoring service offered by Jethro 3.4.2. This would replace local implementation you might have to renew the ticket for Jethro. To set it up and running, the ticket name, path and interval, will need to be configured, using the instructions described in Configuring Kerberos Authentication.

*** If you upgrade from earlier version than V3.40 - see also Jethro 3.4 specific upgrade notes as it requires to run a conversion script. ***

Jethro 3.4.1

*** If you upgrade from earlier version than V3.40 - see also Jethro 3.4 specific upgrade notes as it requires to run a conversion script. ***

Jethro 3.4.0

Before upgrade:

Stop all loads and stop JethroLoadsScheduler service (service jethro stop [instance-name] loadscheduler)
Confirm the load scheduler event drop folder is empty (ls [storage-root-path]/[instance-name]/loads/drop)
Backup schema files to allow easy downgrade if needed (data model is changed by the new version, therefore schema files will be edited).
For HDFS instance:
```
hadoop fs –copyToLocal {instance-location}/metadata/schema* /backup_schema_340/
```
For local instance:
```
cp {instance-location}/metadata/schema* /backup_schema_340/
```
Instance-location can be found in local-conf.ini file as the value of storage.root.path variable.

After upgrade to 3.4.0 it is mandatory to run upgrade tool over each existing instance.
Usage:

upgradeTo3.4_MultiSchema <instance> <ip/localhost>:<port> -u <user> -p <pass>

This tool creates system schema "sys" and move jethro system tables to "sys" schema

Jethro Latest