This process upgrades Ambari Server. It does not change the underlying Hadoop Stack. This is a twelve step manual process.
Note | |
---|---|
You must know the location of the Nagios server for Step 9. Use the Services View-> Summary panel to locate the host on which it is running. |
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/Oracle Linux 5
wget http://public-repo-1.hortonworks.com/ambari/centos5/1.x/updates/1.2.5.17/ambari.repo
For RHEL/CentOS 6/Oracle Linux 6
wget http://public-repo-1.hortonworks.com/ambari/centos6/1.x/updates/1.2.5.17/ambari.repo
For SLES 11
wget http://public-repo-1.hortonworks.com/ambari/suse11/1.x/updates/1.2.5.17/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/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 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.
Upgrade Ambari Server. From the Ambari Server host:
RHEL/CentOS
yum clean all yum upgrade ambari-server-1.2.5.17 ambari-log4j-1.2.5.17
SLES
zypper clean zypper up ambari-server-1.2.5.17 ambari-log4j-1.2.5.17
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-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 updated ... ---> Package ambari-agent.x86_64 0:1.2.2.5-1 will be an update ...
After the process is complete, check each host to make sure the new 1.2.4 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
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
Upgrade the Ambari Server schema. From the Ambari Server host:
ambari-server upgrade
Upgrade the Ambari Agent on all hosts. From each Ambari Agent host:
RHEL/CentOS
yum upgrade ambari-agent ambari-log4j
SLES
zypper up ambari-agent ambari-log4j
Note If you get a warning that begins "There are some running programs that use files deleted by recent upgrade" you can ignore it.
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
Upgrade the Nagios and Ganglia addons package and restart. On the Nagios/Ganglia host:
RHEL/CentOS
yum upgrade hdp_mon_nagios_addons hdp_mon_ganglia_addons service httpd restart
SLES
zypper up hdp_mon_nagios_addons hdp_mon_ganglia_addons service apache2 restart
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
Important 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 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.
Re-start the Ganglia, Nagios, and MapReduce services. In Ambari Web.
Go to the Services View and select each service.
Use the Management Header to stop and re-start each service.