Ambari Managed HDF Upgrade
Also available as:
PDF

Upgrade HDF services

Ensure that you complete these steps on each node that contains an HDF service.

Ensure that you have backed up your SAM and Schema Registry databases.
  1. Confirm HDF components installed along with version (e.g. 3.2.0.0-520).
    [root@host registry]# yum list installed | grep HDF
    
    hdf-select.noarch                 3.2.0.0-520.el6           @HDF-3.2            
    nifi_3_2_0_0_520.x86_64           1.7.0.3.2.0.0-520.el6     @HDF-3.2            
                                      0.7.0.3.2.0.0-520.el6     @HDF-3.2            
    registry_3_2_0_0_520.noarch       0.5.3.3.2.0.0-520.el6     @HDF-3.2           
    storm__3_0_2_0_76.x86_64          1.2.1.3.2.0.0-520.el6     @HDF-3.2            
    streamline_3_0_2_0_76.x86_64      0.6.0.3.2.0.0-520.el6     @HDF-3.2           
    zookeeper_3_0_2_0_76.noarch       3.4.6.3.2.0.0-520.el6     @HDF-3.2         
    
  2. Display the current version associated with each component.
    [root@host registry]# hdf-select status | grep 3.2.0.0-520
    
    nifi - 3.2.0.0-520
    registry - 3.2.0.0-520
    storm-client - 3.2.0.0-520
    storm-nimbus - 3.2.0.0-520
    storm-supervisor - 3.2.0.0-520
    streamline - 3.2.0.0-520
    zookeeper-client - 3.2.0.0-520
    zookeeper-server - 3.2.0.0-520
    
  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_3_0_0_165*
    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.3.0.0-<build-no>
    [root@host ~]# hdf-select set registry 3.3.0.0-<build-no>
    [root@host ~]# hdf-select set streamline 3.3.0.0-<build-no>
    [root@host ~]# hdf-select set storm-nimbus 3.3.0.0-<build-no>
    [root@host ~]# hdf-select set storm-supervisor 3.3.0.0-<build-no>
    [root@host ~]# hdf-select set zookeeper-client 3.3.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.3.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 the HDF components that were updated.
    [root@host ~]# hdf-select status | grep 3.3.0.0-<build-no>
    nifi - 3.3.0.0-<build-no>
    registry - 3.3.0.0-<build-no>
    storm-nimbus - 3.3.0.0-<build-no>
    storm-supervisor - 3.2.0.0-<build-no>
    streamline - 3.3.0.0-<build-no>
    zookeeper-client - 3.3.0.0-<build-no>
    zookeeper-server - 3.3.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, and configurations are available.