Upgrading Ambari Server is a ten step manual process.
Stop the Ambari Server and all Ambari Agents. From the Ambari Server host:
ambari-server stop
From each Ambari Agent host:
ambari-agent stop
Get the new Ambari bits. Use
wget
to fetch the repository file and replace the old repo file with the new repo file on every host.Fetch the new repo file:
For RHEL/CentOS 5
wget http://public-repo-1.hortonworks.com/ambari/centos5/1.x/GA/ambari.repo
For RHEL/CentOS 6
wget http://public-repo-1.hortonworks.com/ambari/centos6/1.x/GA/ambari.repo
For SLES 11
wget http://public-repo-1.hortonworks.com/ambari/suse11/1.x/GA/ambari.repo
Important Check your current directory before you download the new repo 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 repo file with the new repo file.
For RHEL/CentOS 5
cp ambari.repo /etc/yum.repos.d/ambari.repo
For RHEL/CentOS 6
cp ambari.repo /etc/yum.repos.d/ambari.repo
For SLES 11
cp ambari.repo /etc/zypp/repos.d/ambari.repo
Note If your cluster does not have access to the Internet, you need to set up a local repository with this data before you continue. See Configure the Local Repositories for more information.
Local repository installs only: Copy the old stacks definition file (
/var/lib/ambari-server/resources/stacks/HDPLocal/1.2.0/repos/repoinfo.xml
to a safe place. You will be using it in Step 8.Upgrade Ambari Server. From the Ambari Server host:
RHEL/CentOS
yum upgrade ambari-server
SLES
zypper clean --all zypper up ambari-server
Check for upgrade success:
As the process runs, the console should produce output similar to this:
Setting up Upgrade Process Resolving Dependencies --> Running transaction check ---> Package ambari-agent.x86_64 0:1.2.2.3-1 will be updated ---> Package ambari-agent.x86_64 0:1.2.2.4-1 will be an update ...
Once the process is complete, check each host to make sure the new files have been installed:
rpm -qa | grep ambari-*
If the upgrade fails, the console should produce output similar to this:
Setting up Upgrade Process No Packages marked for Update
Rename the config folder for the Server. The name is changed in the upgrade process and must be changed back.
mv /etc/ambari-server/conf.save /etc/ambari-server/conf
Upgrade the Ambari Server schema. From the Ambari Server host:
ambari-server upgrade
Local repository installs only: Take the version of the
repoinfo.xml
file you copied in Step 3, and copy it back to/var/lib/ambari-server/resources/stacks/HDPLocal/1.2.0/repos/repoinfo.xml
.Upgrade the Ambari Agent on all hosts. From each Ambari Agent host:
RHEL/CentOS
yum upgrade ambari-agent
SLES
zypper up ambari-agent
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
Rename the
ambari-agent.ini
file. This name is changed during the upgrade process and must be changed back. On each Agent host::mv /etc/ambari-agent/conf/ambari-agent.ini.rpmsave /etc/ambari-agent/conf/ambari-agent.ini
Upgrade the Nagios addons package and restart the http daemon. On the Nagios host:
RHEL/CentOS
yum upgrade hdp_mon_nagios_addons service httpd restart
SLES
zypper up hdp_mon_nagios_addons service apache2 restart
Note If you do not know which host is running the Nagios server, you can use the Services View Summary panel to locate it.
Start the Server and the Agents on all hosts. From the Server host:
ambari-server start
From each Agent host:
ambari-agent start
Open Ambari Web. Point your browser to
http://{your.ambari.server}:8080
Use the Admin name and password you have set up to log in.
Note If the Install Wizard is displayed, you need to 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 this still does not solve the problem, clear your browser cache and relaunch the browser after restarting Ambari Server.
Re-set the Ambari-Ganglia connection. In Ambari Web.
Go to the Services View and select the Ganglia service.
Use the Management Header to stop and re-start the Ganglia service.