Prerequisites for Upgrade
This page explains how to back up the database, increase the NameNode timeout value, prepare for an upgrade, and view unsupported components.
Increase the NameNode Timeout Value
To ensure that Ambari requests to start the NameNode and does not timeout during an upgrade, you must configure the Ambari NameNode restart timeout parameter using upgrade.parameter.nn-restart.timeout in the /etc/ambari-server/conf/ambari.properties file on the Ambari Server host.
You may need to add the restart timeout parameter and value to the Ambari server host following a default installation. For a large cluster, you must add 50% to the usual time (in seconds) that is required to restart the NameNode.
For example, on the Ambari server, observe the time (in seconds) required to restart the active NameNode. If the time taken to restart the active NameNode is more than 10 minutes (600 seconds) and the cluster is large, then add the following parameter to the /etc/ambari-server/conf/ambari.properties file on the Ambari Server host.
parameter.upgrade.parameter.nn-restart.timeout=900
After adding or resetting the Ambari NameNode restart parameter, restart the Ambari server before upgrading it to a newer version using the below command.
ambari-server restart
Unsupported components
1. Remove Unsupported Components
To remove unsupported Management Packs (MPACKs) before upgrading, complete the following steps on the Ambari Server host.
- Clone the ce-utils repository:
git clone https://github.com/acceldata-io/ce-utils.git
- Navigate to the scripts directory:
cd ce-utils/ODP/scripts/
- Run the MPACK service removal script:
bash ambari_delete_mpack_service.sh
- Example output:
┌────────────────────────────────────────────────────────────┐
│ Ambari MPACK Service Removal Tool │
└────────────────────────────────────────────────────────────┘
AMBARISERVER : odp34upg1
AMBARI_USER : admin
AMBARI_PASSWORD : ********
PORT : 8080
PROTOCOL : http
AMBARI_RESOURCES : /var/lib/ambari-server/resources
BACKUP_DIR : /home/acceldata/ce-utils/ODP/scripts/upgrade_backup
PYTHON_BIN : /bin/python3
[INFO] Cluster identified : odp34upg
[INFO] Stack : ODP-3.3
MPACK-installed services in 'odp34upg'
(use --all to see every service):
# SERVICE STATE SOURCE
--- ------------ ---------- -----------------------------------------
1 AIRFLOW STARTED MPACK (airflow-ambari-mpack-2.8.3)
2 CLICKHOUSE STARTED MPACK (clickhouse-25.5.4.38-mpack-25.5.4.38)
3 FLINK STARTED MPACK (flink-ambari-mpack-1.19.1)
4 HTTPFS STARTED MPACK (httpfs-ambari-mpack-2.7.1)
5 HUE STARTED MPACK (hue-ambari.mpack-4.11.0)
6 IMPALA STARTED MPACK (ambari-impala-mpack-4.4.1)
7 JUPYTER STARTED MPACK (jupyter-ambari-mpack-5.2.1)
8 KUDU STARTED MPACK (kudu-ambari-mpack-1.17.0)
9 MLFLOW STARTED MPACK (mlflow-ambari-mpack-3.1.0)
10 PINOT STARTED MPACK (pinot-ambari-mpack-1.3.0)
11 REGISTRY STARTED MPACK (registry-ambari-mpack-1.0.0)
12 SPARK3 STARTED MPACK (spark3-ambari-3.5.5.mpack-3.5.5)
13 TRINO STARTED MPACK (trino-ambari-mpack-472)
Enter the number(s) of the service(s) to STOP and DELETE
(comma-separated, or 'q' to quit): 2, 3, 6, 8, 9, 11, 12, 13
- Identify the MPACKs that must be removed before upgrading.
Warning: The following MPACKs currently support upgrades; ensure NOT to DELETE them:
- JupyterHub
- Impala
- Hue
- Pinot
- Kafka3
- HTTPFS
Info: The example selects services 2, 3, 8, 9, 11, 12, 13 for removal. However, Impala appears in both the supported MPACK list and the removal selection.
- Select the services to remove. The script stops the selected services, backs up their configurations, and deletes them from the cluster.
Example output:
The following service(s) will be STOPPED, their configs
BACKED UP to
/home/acceldata/ce-utils/ODP/scripts/upgrade_backup,
then DELETED from cluster 'odp34upg':
- CLICKHOUSE [MPACK: clickhouse-25.5.4.38-mpack-25.5.4.38]
- FLINK [MPACK: flink-ambari-mpack-1.19.1]
- IMPALA [MPACK: ambari-impala-mpack-4.4.1]
- KUDU [MPACK: kudu-ambari-mpack-1.17.0]
- MLFLOW [MPACK: mlflow-ambari-mpack-3.1.0]
- REGISTRY [MPACK: registry-ambari-mpack-1.0.0]
- SPARK3 [MPACK: spark3-ambari-3.5.5.mpack-3.5.5]
- TRINO [MPACK: trino-ambari-mpack-472]
Type DELETE to proceed: DELETE
- Type DELETE to confirm the removal of the selected services.
The script stops each service and backs up its configurations before deleting it.
Example output:
=== CLICKHOUSE ===
[INFO] Stopping CLICKHOUSE ...
request 21: COMPLETED
100%
[INFO] Backing up configurations of CLICKHOUSE ...
clickhouse-application (tag TOPOLOGY_RESOLVED)
-> /home/acceldata/ce-utils/ODP/scripts/upgrade_backup/
clickhouse-application/clickhouse-application.json
...
[WARN] The following password properties of CLICKHOUSE
[WARN] are stored as SECRET references and
[WARN] will NOT be recoverable once the service is deleted.
[WARN] Note their values now
[WARN] (Ambari UI -> CLICKHOUSE -> Configs, or the Ambari DB):
clickhouse-remote-servers :
"cluster_secret": "SECRET:clickhouse-remote-servers:2:cluster_secret"
Have you recorded these passwords?
Type 'yes' to continue with CLICKHOUSE: yes
- Important: Some password properties are stored as secret references and cannot be recovered after the service is deleted. Record these values securely before proceeding. You can retrieve them from the Ambari UI or the Ambari database.
- Type yes to confirm that you have recorded the required passwords and continue with the service removal.
- Uninstall the MPACKs by running the following commands on the Ambari Server host:
ambari-server uninstall-mpack --mpack-name=ambari-impala-mpack
ambari-server uninstall-mpack --mpack-name=clickhouse-25.5.4.38-mpack
ambari-server uninstall-mpack --mpack-name=flink-ambari-mpack
ambari-server uninstall-mpack --mpack-name=kudu-ambari-mpack
ambari-server uninstall-mpack --mpack-name=mlflow-ambari-mpack
ambari-server uninstall-mpack --mpack-name=registry-ambari-mpack
ambari-server uninstall-mpack --mpack-name=spark3-ambari-3.5.5.mpack
ambari-server uninstall-mpack --mpack-name=trino-ambari-mpack
- Important: Uninstall only the MPACKs that are confirmed to be unsupported for the target ODP version and whose services have been removed.
- Restart the Ambari Server to apply the changes:
ambari-server restart
Have a suggestion?