Ambari Managed HDF Upgrade
Also available as:
PDF

Upgrade HDF services

Ensure that you have backed up your SAM and Schema Registry databases.
  1. Confirm HDF components installed along with version (e.g. 3.0.2.0-76).
    [root@host registry]# yum list installed | grep HDF
    
    hdf-select.noarch                 3.0.2.0-76.el6           @HDF-3.0            
    nifi_3_0_2_0_76.x86_64           1.2.0.3.0.2.0-76.el6     @HDF-3.0            
                                      0.7.0.3.0.2.0-76.el6     @HDF-3.0            
    registry_3_0_2_0_76.noarch       0.3.0.3.0.2.0-76.el6     @HDF-3.0            
    storm__3_0_2_0_76.x86_64          1.1.0.3.0.2.0-76.el6     @HDF-3.0            
    streamline_3_0_2_0_76.x86_64     0.5.0.3.0.2.0-76.el6     @HDF-3.0            
    zookeeper_3_0_2_0_76.noarch      3.4.6.3.0.2.0-76.el6     @HDF-3.0          
    
  2. Display the current version associated with each component (in following example 3.0.2.0-76 is current version).
    [root@host registry]# hdf-select status | grep 3.0.2.0-76
    
    nifi - 3.0.2.0-76
    registry - 3.0.2.0-76
    storm-client - 3.0.2.0-76
    storm-nimbus - 3.0.2.0-76
    storm-supervisor - 3.0.2.0-76
    streamline - 3.0.2.0-76
    zookeeper-client - 3.0.2.0-76
    zookeeper-server - 3.0.2.0-76
    
  3. Install binaries for the HDF services to which you want to upgrade.

    See the HDF Release Notes for the repository information, including service version and build number.

    [root@host ~]# yum install -y <service>_<version>_<build-number>*

    For example:

    [root@host ~]# yum install -y nifi_3_2_0_0_520*
    Note
    Note
    Only run the yum install command on Ambari Agent hosts where NiFi is already installed.
  4. Use hdf-select to ensure appropriate links to new installed version. Note that SAM also brings down Storm and ZooKeeper dependencies that also needs to be accounted for.
    For example,
    [root@host ~]# hdf-select set nifi 3.2.0.0-<build-no>
    [root@host ~]# hdf-select set registry 3.2.0.0-<build-no>
    [root@host ~]# hdf-select set streamline 3.2.0.0-<build-no>
    [root@host ~]# hdf-select set storm-nimbus 3.2.0.0-<build-no>
    [root@host ~]# hdf-select set storm-supervisor 3.2.0.0-<build-no>
    [root@host ~]# hdf-select set zookeeper-client 3.2.0.0-<build-no>
    
    WARNING: Replacing link /usr/bin/zookeeper-client from /usr/hdp/current/zookeeper-client/bin/zookeeper-client
    
    [root@host ~]# hdf-select set zookeeper-server 3.2.0.0-<build-no>
    
    WARNING: Replacing link /usr/bin/zookeeper-server from /usr/hdp/current/zookeeper-server/bin/zookeeper-server
    WARNING: Replacing link /usr/bin/zookeeper-server-cleanup from /usr/hdp/current/zookeeper-server/bin/zookeeper-server-cleanup
    
  5. Confirm that hdf select shows new version for hdf components that were updated.
    [root@host ~]# hdf-select status | grep 3.2.0.0-<build-no>
    nifi - 3.2.0.0-<build-no>
    registry - 3.2.0.0-<build-no>
    storm-nimbus - 3.2.0.0-<build-no>
    storm-supervisor - 3.2.0.0-<build-no>
    streamline - 3.2.0.0-<build-no>
    zookeeper-client - 3.2.0.0-<build-no>
    zookeeper-server - 3.2.0.0-<build-no>
    
  6. Log into Ambari and start NiFi, NiFi Registry, SAM and Schema Registry. Confirm all applications started and pre-existing flows/topologies/configurations are available.