Upgrade Ambari Server

Follow the steps below 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

Take the backup of ambari-server configs.

/etc/ambari-server/conf/

Bash
    
xxxxxxxxxx
 
ambari-server stop
Copy

Stop Agents

Stop Ambari-agent on every cluster node.

Bash
    
xxxxxxxxxx
 
ambari-agent stop
Copy

Back up Ambari Database

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

DB Backup Commands

Bash
    
xxxxxxxxxx
 
mkdir /tmp/ambari-server_db_bckpmysqldump --databases ambari > /tmp/ambari-server_db_bckp/ambari_mysql_bckp.sql
Copy

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:

Bash
    
xxxxxxxxxx
 
mv /etc/yum.repos.d/ambari.repo /tmp/
Copy

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

List the existing Ambari packages

On RHEL:

Bash
    
xxxxxxxxxx
 
rpm -qa | grep ambari
Copy

On Ubuntu:

Bash
    
xxxxxxxxxx
 
apt list ambari-*
Copy

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

Bash
    
xxxxxxxxxx
 
ambari-infra-solr-3.0.0.1-1.noarchambari-agent-3.0.0.1-1.x86_64ambari-server-3.0.0.1-1.x86_64ambari-infra-solr-client-3.0.0.1-1.noarch
Copy

Remove existing Ambari rpm’s

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

On RHEL:

Bash
    
xxxxxxxxxx
 
yum remove ambari-server
Copy

On Ubuntu:

Bash
    
xxxxxxxxxx
 
apt remove ambari-server
Copy

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:

Bash
    
xxxxxxxxxx
 
rpm -qa | grep ambari
Copy

On Ubuntu:

Bash
    
Copy

Make sure the Amabri packages are not installed.

If you are upgrading from any Python 2 based ODP version, make sure to perform the below additional steps to install Python 3.11 and its dependencies on all the hosts before proceeding with the next step.

For Ubuntu 20/22:

Bash
    
Copy

For RHEL 8:

Bash
    
Copy

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

Server Node

On RHEL:

Bash
    
Copy

On Ubuntu:

Bash
    
Copy

Set up Java 17

Make sure to install and update the default Java version as 17 on all the cluster nodes.

For RHEL:

Bash
    
Copy

For Ubuntu:

Bash
    
Copy

Ensure not to remove the jdk8 packages at this state.

Bash
    
Copy

Set up Python 3.11

Bash
    
Copy

Make sure to install and update the default Python version as 3.11 on all the cluster nodes.

Bash
    
Copy

Update JSVC

Make sure to Instal the latest version of the bigtop-jsvc-1.2.4 on all the cluster nodes.

For RHEL:

Bash
    
Copy

For Ubuntu:

Bash
    
Copy

Restore Config Files

Restore the ambari.properties and password.dat files, which are backed up at this step: Configuration Backup on this page.

Restore the ambari.properties file

Bash
    
Copy

Please override the file by prompting 'y'.

Restore the password.dat file

Bash
    
Copy

Update the java.home and stack.java.home

In this case, set JAVA_HOME to /usr/lib/jvm/java-17-openjdk

File path - /etc/ambari-server/conf/ambari.properties | grep -i java.home

Bash
    
Copy

Update the Ambari Database with New Tables and Columns

MySQL

Bash
    
Copy

MariaDB

Bash
    
Copy

Bash
    
Copy

Oracle 19C

Bash
    
Copy

Ambari Server Schema Upgrade

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

Run the Ambari Server upgrade command:

Bash
    
Copy

If you encounter the following error:

Bash
    
Copy

Set up the Distro Module

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

On RHEL:

Bash
    
Copy

Bash
    
Copy

On Ubuntu:

Bash
    
Copy

Retry the Upgrade again

Bash
    
Copy

Response when prompted:

Bash
    
Copy

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

Bash
    
Copy

Start Ambari-server

Bash
    
Copy

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.

Bash
    
Copy

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

For MySQL

Bash
    
Copy

Bash
    
Copy

The response is as follows.

Bash
    
Copy

Verify the data.

Bash
    
Copy

Rename the table groups to groups_info using the following command.

Bash
    
Copy

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

Bash
    
Copy

For Oracle

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

Bash
    
Copy

The response is as follows.

Bash
    
Copy

Rename the table groups to groups_info using the following command.

Bash
    
Copy

The successful rename operation results the output as TABLE Renamed.

Verify the data once renaming is completed.

For Postgres

Log in to the Postgres server hosting the Ambari database.
Verify the existing GROUPS table.

Bash
    
Copy

The response is as follows.

Bash
    
Copy

Rename the table groups to groups_info using the following command.

Bash
    
Copy

Last updated on May 14, 2026

Was this page helpful?