Upgrade Ambari Server

Follow the below steps to upgrade the Ambari version.

Stop Infra-solr Service

Stop the Infra-solr Service from Ambari-UI.

Stop Ambari Server and Agents

Stop Ambari Server

xxxxxxxxxx

ambari-server stop

Stop Agents

Stop Ambari-agent on every cluster nodes.

xxxxxxxxxx

ambari-agent stop

Back up Ambari Database

Take the Ambari-server backend database backup from the server host.

DB Backup Commands

xxxxxxxxxx

mkdir /tmp/ambari-server_db_bckp

mysqldump --databases ambari > /tmp/ambari-server_db_bckp/ambari_mysql_bckp.sql

The upgraded version Ambari-2.7.8.2-3 supports only Python 3.11. Ensure that Python 3.11 is installed and configured on all the cluster nodes before proceeding with the upgrade.

Add Ambari Repo on Cluster Nodes

Back up the Old Ambari Repository

Run the following command:

xxxxxxxxxx

mv /etc/yum.repos.d/ambari.repo /tmp/

Retrieve the latest Ambari repository details from Accessing Acceldata Repositories and add it to all cluster nodes.

List the existing Ambari packages

On RHEL:

xxxxxxxxxx

rpm -qa | grep ambari

On Ubuntu:

xxxxxxxxxx

apt list ambari-*

Example Output (if the current Ambari version is 2.7.9.2-1):

xxxxxxxxxx

ambari-infra-solr-2.7.9.2-1.noarch

ambari-agent-2.7.9.2-1.x86_64

ambari-server-2.7.9.2-1.x86_64

ambari-infra-solr-client-2.7.9.2-1.noarch

Remove existing Ambari rpm’s

From the Ambari Server node, remove the installed packages before upgrading:

On RHEL:

xxxxxxxxxx

yum remove ambari-server

On Ubuntu:

xxxxxxxxxx

apt remove ambari-server

Note

• Adjust the package names based on the installed versions on each node.
• You can verify the installed packages before removing them using:

On RHEL:

xxxxxxxxxx

rpm -qa | grep ambari

On Ubuntu:

xxxxxxxxxx

apt list ambari-*

Make sure the Amabri packages are not installed.

Install Ambari packages

For Ubuntu 20/22:

xxxxxxxxxx

apt install software-properties-common

add-apt-repository ppa:deadsnakes/ppa

apt update

apt-get install python3.11 

curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py

/usr/bin/python3.11 get-pip.py

pip3.11 install distro lxml

For RHEL 8:

xxxxxxxxxx

yum install python3.11 python3.11-pip 

pip3.11 install distro lxml

Install the latest Ambari-server only on ambari-server node.

Server Node

On RHEL:

On Ubuntu:

Ambari Server Configuration Files Restore

Restore the configuration files backed up at step4 (Backup taken in step 4).

Restore ambari.properties File

When prompted, enter 'y' to confirm.

Restore passwd.dat File

Ambari Server Schema Upgrade

Before upgrading, ensure a database backup has been taken (as mentioned in Step 6).

Run the Ambari Server upgrade command:

If you encounter the following error:

Set up the Distro Module

Install the required dependencies on the ambari-server and ambari-agent nodes.

On RHEL:

On Ubuntu:

Retry the Upgrade again

Response when prompted:

After the successful completion, you must see the following message.

Start Ambari-server

Once started, verify that the Ambari UI is accessible using the same URL as before.

Verify Ambari Version

Verify the upgraded Ambari version in admin->about on top right corner in Ambari UI.

The Ambari version is upgraded successfully.

Upgrade Known Issues

During the migration, the existing GROUPS table in the Ambari database might cause conflicts due to its name. As a result, the Ambari UI might fail to start and throw the following error when attempting to log in.

To resolve this issue, rename the GROUPS table to groups_info in the Ambari backend database.

For MySQL

1. Log into the MySQL server hosting the Ambari database.

2. The response is as follows.

3. Verify the data.

4. Rename the table groups to groups_info using the following command.

5. Verify the same data as it was in groups table earlier. It must have the same data as it was earlier in groups table.

For Oracle

1. Log into the Oracle server hosting the Ambari database.
2. Verify the existing GROUPS table.

3. The response is as follows.

4. Rename the table groups to groups_info using the following command.

The successful rename operation results the output as TABLE Renamed.

4. Verify the data once renaming is completed.

For Postgres

1. Log into the Postgres server hosting the Ambari database.
2. Verify the existing GROUPS table.

3. The response is as follows.

4. Rename the table groups to groups_info using the following command.