DocsHortonworks Data Platform

 

 Chapter 1. Upgrading Ambari Server to 1.6.1

This procedure upgrades Ambari Server from version 1.2.5 and above to 1.6.1. If your current Ambari Server version is 1.2.4 or below, you must upgrade the Ambari Server version to 1.2.5 before upgrading to version 1.6.1. Upgrading the Ambari Server version does not change the underlying Hadoop Stack.

[Note]Note

You must know the location of the Nagios server for Step 9. Use Ambari Web > Services View > Summary to locate the host on which it is running.

  1. Stop the Nagios and Ganglia services. In Ambari Web:

    1. Browse to Services and select each service.

    2. Use Service Actions to stop the service.

  2. Stop the Ambari Server and all Ambari Agents. From the Ambari Server host:

    ambari-server stop

    From each Ambari Agent host:

    ambari-agent stop

  3. Get the new Ambari bits. Use wget to fetch the repository file and replace the old repository file with the new repository file on every host.

    • Fetch the new repository file:

      For RHEL/CentOS 5/Oracle Linux 5

      wget http://public-repo-1.hortonworks.com/ambari/centos5/1.x/updates/1.6.1/ambari.repo

      For RHEL/CentOS 6/Oracle Linux 6

      wget http://public-repo-1.hortonworks.com/ambari/centos6/1.x/updates/1.6.1/ambari.repo

      For SLES 11

      wget http://public-repo-1.hortonworks.com/ambari/suse11/1.x/updates/1.6.1/ambari.repo
      [Important]Important

      Check your current directory before you download the new repository file to make sure that there are no previous versions of the 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.

    • Replace the old repository file with the new repository file.

      For RHEL/CentOS 5/Oracle Linux 5

      cp ambari.repo /etc/yum.repos.d/ambari.repo

      For RHEL/CentOS 6/Oracle Linux 6

      cp ambari.repo /etc/yum.repos.d/ambari.repo

      For SLES 11

      cp ambari.repo /etc/zypp/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. See Configure the Local Repositories for more information.

  4. Upgrade Ambari Server.

    [Note]Note

    Ambari Server no longer automatically turns iptables off. Check your installation setup to make sure that you are not relying on this function. After you have upgraded the server you must either disable iptables manually or make sure that you have all the appropriate ports available.

    From the Ambari Server host:

    • RHEL/CentOS/Oracle Linux

      yum clean all
yum upgrade ambari-server ambari-log4j

    • SLES

      zypper clean
zypper up ambari-server ambari-log4j

  5. Check for upgrade success:

    • As the process runs, the console should produce output similar, although not identical, to this:

      Setting up Upgrade Process
Resolving Dependencies
--> Running transaction check
---> Package ambari-server.x86_64 0:1.2.2.3-1 will be updated
---> Package ambari-server.x86_64 0:1.2.2.4-1 will be updated ...
---> Package ambari-server.x86_64 0:1.2.2.5-1 will be an update ...

    • If the upgrade fails, the console should produce output similar to this:

      Setting up Upgrade Process
No Packages marked for Update

  6. Check to see if you have a folder named /etc/ambari-server/conf.save. If you do, rename it back:

    mv /etc/ambari-server/conf.save /etc/ambari-server/conf

  7. Upgrade the Ambari Server schema. From the Ambari Server host:

    ambari-server upgrade

  8. Upgrade the Ambari Agent on all hosts. From each Ambari Agent host:

    • RHEL/CentOS/Oracle Linux

      yum upgrade ambari-agent ambari-log4j

    • SLES

      zypper up ambari-agent ambari-log4j
      [Note]Note

      Ignore the warning that begins with "There are some running programs that use files deleted by recent upgrade".

  9. Check to see if you have a file named /etc/ambari-agent/conf.save on each Agent host. If you do, rename it back. On each Agent host:

    mv /etc/ambari-agent/conf.save /etc/ambari-agent/conf

  10. Upgrade the Nagios add-ons package. On the Nagios host:

    • RHEL/CentOS/Oracle Linux

      yum upgrade hdp_mon_nagios_addons

    • SLES

      zypper up hdp_mon_nagios_addons

  11. After the process is complete, check each host to make sure the new 1.6.1 files have been installed:

    rpm -qa | grep ambari

  12. Start the Server and the Agents on all hosts. From the Server host:

    ambari-server start

    From each Agent host:

    ambari-agent start

  13. Open Ambari Web. Point your browser to http://{your.ambari.server}:8080

    [Important]Important

    Refresh your browser so that it loads the new version of the code. Hold the Shift key down while clicking the refresh button on the browser. If you have problems, clear your browser cache manually and restart Ambari Server.

    Use the Admin name and password you have set up to log in.

  14. Start the Nagios and Ganglia services. In Ambari Web:

    1. Browse to Services and select each service.

    2. Use Service Actions to start the service.

  15. If you have customized logging properties, you will see refresh indicators next to each service name after upgrading to Ambari 1.6.1.

    [Note]Note

    Restarting a service pushes the configuration properties displayed in Custom log4j.properties to each host running components for that service.

    To preserve any custom logging properties after upgrading, for each service:

    1. Replace default logging properties with your custom logging properties, using Service Configs -> Custom log4j.properties.

    2. Restart all components in any services for which you have customized logging properties.

      For more information about logging properties, see Customizing Your Logging Properties.

  16. Review HDP-UTILS repository Base URL setting.

    [Note]Note

    As of Ambari 1.6.1, the HDP-UTILS repository Base URL is no longer set in the ambari.repo file.

    Browse to Ambari Web > Admin > Clusters, and confirm the value of the HDP-UTILS repository Base URL is correct for your environmnet. See Managing Stack Repositories for more information.

    [Important]Important

    If you are using a local repository for HDP-UTILS, be sure to confirm the Base URL is correct for your locally hosted HDP-UTILS repository.

Legal notices