IOP to HDP Migration
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. ONLY IF migrating from IOP-4.2.0, upgrade Ambari to version 2.5.2.

    [Important]Important

    If migrating from IOP-4.2.5, skip this step and proceed with step 5.

    1. Fetch the Ambari-2.5.2 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:

      • For RHEL/CentOS/Oracle Linux 6:

        wget -nv http://public-repo-1.hortonworks.com/ambari/centos6/2.x/BUILDS/2.5.2.0/ambari.repo -O /etc/yum.repos.d/ambari.repo
      • For RHEL/CentOS/Oracle Linux 7:

        wget -nv http://public-repo-1.hortonworks.com/ambari/centos7/2.x/BUILDS/2.5.2.0/ambari.repo -O /etc/yum.repos.d/ambari.repo
      • For IBM Power Systems:

        wget -nv http://public-repo-1.hortonworks.com/ambari/centos7-ppc/2.x/updates/2.5.2.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 before you continue.

      [Note]Note

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

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

      yum clean all
      yum info ambari-server

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

      yum upgrade ambari-server ambari-agent
    3. 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-2.5.2.0-220.x86_64 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 other ambari-server*.jar files except for the ambari-server-2.5.2.jar to /tmp before proceeding with upgrade.

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

      yum upgrade ambari-agent
      [Note]Note

      If you will immediately upgrade Ambari to version 2.6.1 , upgrading the agents to version 2.5.2 is optional.

    5. After the upgrade process completes, check each host to make sure the new files have been installed:

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

      ambari-server upgrade
  5. Upgrade Ambari to version 2.6.1.

    1. Fetch the Ambari-2.6.1 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:

      • For RHEL/CentOS/Oracle Linux 6:

        wget -nv http://public-repo-1.hortonworks.com/ambari/centos6/2.x/BUILDS/2.6.1.0/ambari.repo -O /etc/yum.repos.d/ambari.repo
      • For RHEL/CentOS/Oracle Linux 7:

        wget -nv http://public-repo-1.hortonworks.com/ambari/centos7/2.x/BUILDS/2.6.1.0/ambari.repo -O /etc/yum.repos.d/ambari.repo
      • For IBM Power Systems:

        wget -nv http://public-repo-1.hortonworks.com/ambari/centos7-ppc/2.x/updates/2.6.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 before you continue.

      [Note]Note

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

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

      yum clean all
      yum info ambari-server

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

      yum upgrade ambari-server ambari-agent
    3. 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-2.6.1.0-143.x86_64 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 other ambari-server*.jar files except for the ambari-server-2.6.1.jar to /tmp before proceeding with upgrade.

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

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

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

      ambari-server upgrade
  6. If you have configured Ambari to authenticate using LDAP or Active Directory, you must re-run

    ambari-server setup-ldap
  7. 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={database-type} --jdbc-driver={/jdbc/driver/path}

    to get the appropriate JDBC driver .jar file in place. For example:

    ambari-server setup --jdbc-db=mysql --jdbc-driver=/usr/share/java/mysql-connector-java.jar
  8. If the original IOP cluster was configured for a non-root user, you must update /etc/sudoers file using the visudo command in all the nodes in your cluster, to remove sudoer permissions for the non-root user added in IOP non-root configuration. You should refresh the sudoers file to the original settings, as described here.

  9. Start the Ambari Server. On the host running Ambari Server:

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

    ambari-agent start
  11. 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.

  12. 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. The 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 Ambari-2.6.1. Review these changes by comparing the previous configuration with the latest version created by the Ambari upgrade.

    [Note]Note

    HDFS may fail to restart after upgrading Ambari on a NameNode HA-enabled, IOP cluster.

    To resolve this issue, see Troubleshooting Migration Issues.

Next Steps

Post-Upgrade Tasks Mandatory

[Important]Important

Completing post-upgrade tasks is mandatory.

More Information

Using a Local Repository

Configuring Network Port Numbers

Set Up LDAP or Active Directory Authentication

Upgrade Ambari Metrics

Add Grafana