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

Upgrade Ambari

  1. If you are running Ambari Metrics service in your cluster, stop the service. From Ambari Web, browse to Services > Ambari Metrics and select Stop from the Service Actions menu.

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

    ambari-server stop
  3. Stop all Ambari Agents. On each host in your cluster running an Ambari Agent:

    ambari-agent stop
  4. 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 https://archive.cloudera.com/p/ambari/2.x/2.5.2.0/centos7-ppc/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.

  5. 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.5"

    yum upgrade ambari-server
  6. 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.5.2-111 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.5.2.jar to /tmp before proceeding with upgrade.

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

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

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

    ambari-server upgrade
  10. Start the Ambari Server. On the host running Ambari Server:

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

    ambari-agent start
  12. Open Ambari Web.

    Point your browser to http://<your.ambari.server>:8080

    where <your.ambari.server> is the name of your ambari server host. For example, c6401.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.

  13. 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".

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

    ambari-server setup-ldap
  15. If you have configured your cluster for Hive 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.

  16. If you are running Ambari Metrics service in your cluster, you must upgrade Ambari Metrics System and add the Grafana component.

  17. If your cluster includes the SmartSense service, you must upgrade SmartSense along with Ambari.

  18. Perform any other post-upgrade tasks, as necessary.

[Important]Important

Completing post-upgrade tasks is mandatory.

Next Steps

Post-Upgrade Tasks Mandatory

More Information

Using a Local Repository

Configuring Network Port Numbers

Set Up LDAP or Active Directory Authentication

Using Non-Default Databases - Hive

Using Non-Default Databases - Oozie

Upgrade Ambari Metrics

Upgrade SmartSense