Apache Ambari Upgrade for IBM Power Systems
Also available as:
PDF

Upgrade Ambari

  1. Turn off Auto Restart from Ambari Web by browsing to Admin > Service Auto Start. Set Auto-Start Services to Disabled. Click Save.

    From Ambari Web, browse to Admin > Service Auto Start. Set Auto-Start Services to Disabled. Click Save.

  2. If you are running SmartSense in your cluster, stop the service.

    From Ambari Web, browse to Services > SmartSense and select Stop from the Service Actions menu. Then, select Turn on Maintenance Mode from the Service Actions menu.

  3. If you are running Ambari Metrics in your cluster, stop the service and put it in Maintenance Mode.

    From Ambari Web, browse to Services > Ambari Metrics and select Stop from the Service Actions menu. Then, select Turn on Maintenance Mode from the Service Actions menu.

  4. If you are running Log Search in your cluster, stop the service.

    From Ambari Web, browse to Services > Log Search and select Stop from the Service Actions menu. Then, select Turn on Maintenance Mode from the Service Actions menu.

  5. Stop the Ambari Server. On the host running Ambari Server:

    ambari-server stop
  6. Fetch the new Ambari repo and replace the old repository file with the new repository file on all hosts in your cluster.

    [Important]Important

    Check your current directory before you download the new repository file to make sure that there are no previous versions of the ambari.repo file. If you do not, and a previous version exists, the new download will be saved with a numeric extension, such as ambari.repo.1. Make sure that the version you copy is the new version.

    Select the repository appropriate for your environment:

    wget -nv http://public-repo-1.hortonworks.com/ambari/centos7-ppc/2.x/updates/2.7.1.0/ambari.repo -O /etc/yum.repos.d/ambari.repo
    [Note]Note

    If your cluster does not have access to the Internet, set up a local repository with this data before you continue.

    [Note]Note

    Ambari Server does not automatically turn off iptables. Check that your installation setup does not depend on iptables being disabled. After upgrading the server, you must either disable iptables manually or make sure that you have appropriate ports available on all cluster hosts.

  7. Upgrade Ambari Server. On the host running Ambari Server:

    For RHEL/CentOS/Oracle Linux:

    yum clean all
    yum info ambari-server

    In the info output, visually validate that there is an available version containing "2.7"

    yum upgrade ambari-server
  8. Check for upgrade success by noting progress during the Ambari Server installation process you started in Step 5.

    • As the process runs, the console displays output similar, although not identical, to the following:

      Setting up Upgrade Process Resolving Dependencies --> Running transaction check

    • If the upgrade fails, the console displays output similar to the following:

      Setting up Upgrade Process No Packages marked for Update

    • A successful upgrade displays output similar to the following:

      Updated: ambari-server.noarch 0:2.7.1 Complete!

    [Note]Note

    Confirm there is only one ambari-server*.jar file in /usr/lib/ambari-server. If there is more than one JAR file with name ambari-server*.jar, move all JARs except ambari-server-2.7.1*.jar to /tmp before proceeding with upgrade.

  9. Upgrade all Ambari Agents. On each host in your cluster running an Ambari Agent:

    yum upgrade ambari-agent
  10. After the upgrade process completes, check each host to make sure the new files have been installed:

    rpm -qa | grep ambari-agent
  11. Upgrade Ambari Server database schema. On the host running Ambari Server:

    ambari-server upgrade

    When the Ambari Server database schema has been upgraded, you should see command output like this:

    Ambari Server ‘upgrade’ completed successfully
  12. Start the Ambari Server. On the host running Ambari Server:

    ambari-server start
  13. Start all Ambari Agents. On each host in your cluster running an Ambari Agent:

    ambari-agent start
  14. Open Ambari Web.

    • When Ambari Server is configured for HTTPS:

      https://<your.ambari.server>:8443

    • When Ambari Server is configured for HTTP:

      http://<your.ambari.server>:8080

    where <your.ambari.server> is the name of your ambari server host. For example, c7401.ambari.apache.org.

    [Important]Important

    Refresh your browser so that it loads the new version of the Ambari Web code. If you have problems, clear your browser cache manually, then restart Ambari Server.

  15. Log in, using the Ambari administrator credentials that you have set up.

    For example, the default name/password is admin/admin.

    You will see a Restart indicator next to each service after upgrading. Ambari upgrade has added to/adjusted the configuration properties of your cluster based on new configuration types and properties being made available for each service with this release of Ambari. Review these changes by comparing the previous configuration with the latest version created by "ambari-upgrade".

    [Important]Important

    DO NOT RESTART these services unless future steps in the upgrade guide prompt you to do so. Manually restarting these services may significantly disrupt your upgrade. Ambari will restart each service automatically during the HDP upgrade.

  16. If you have configured Ambari to authenticate against an external LDAP or Active Directory, you must re-run

    ambari-server setup-ldap
  17. If you have configured your cluster for Hive, Ranger, or Oozie with an external database (Oracle, MySQL or PostgreSQL), you must re-run

    ambari-server setup --jdbc-db and --jdbc-driver

    to get the JDBC driver .jar file in place.

    [Important]Important

    Ambari Metrics System, and SmartSense must be upgraded after first registering the HDP 3.0.x version and installing HDP 3.0.x packages. Please do not attempt to start Ambari Metrics or SmartSense until the HDP 3.0.x upgrade has completed.

More Information

Configuring Ambari Authentication for LDAP/AD

Using a new or existing database with Hive

Using an existing database with Oozie

Configuring a Database Instance for Ranger

​Install Databases for HDF services