Set up Guide

This page describes how to deploy ODP with Azul Prime (Zing) and how to migrate an existing Ambari 3.0.0.0-104 cluster from OpenJDK to Azul Prime. It also covers additional configuration requirements for Pinot and Cruise Control.

Fresh Deployment

During Ambari Server setup, configure Azul Prime (Zing) JDK 11 as the default and stack Java runtime, and OpenJDK 17 as the Ambari Server Java runtime. Then continue with the remaining setup steps described in Set up the Ambari Server.

ambari-server setup -s \
-j <ZING_JDK_INSTALL_PATH> \
--ambari-java-home /usr/lib/jvm/java-17-openjdk \
--stack-java-home <ZING_JDK_INSTALL_PATH> \
--database=postgres \
--databasehost=localhost \
--databaseport=5432 \
--databasename=ambari \
--databaseusername=ambari \
--databasepassword=<DB_PASSWORD>
Enable Azul Prime JVM tuning and start Ambari Server:

ambari-server setup-jvm-tuning azul-prime
ambari-server start

Switching an Existing Ambari 3.0.0.0-104 Cluster from OpenJDK to Azul Prime

On the Ambari Server host, run the following commands:

ambari-server setup -s \
-j <ZING_JDK_INSTALL_PATH> \
--stack-java-home <ZING_JDK_INSTALL_PATH>
Enable Azul Prime JVM tuning and restart Ambari Server:

ambari-server setup-jvm-tuning azul-prime
ambari-server restart
After Ambari Server restarts, restart all stack services from the Ambari UI. Once the restart is complete, all ODP stack services will run on Azul Prime (Zing) JDK.

Additional Configuration for Pinot and Cruise Control

For Pinot and Cruise Control, configure the Java home manually in the Ambari UI.

Set the Java home value for both components to the Azul Prime (Zing) JDK installation path.