6. Update the HDP Cluster Properties File

To keep the same metadata and user data when upgrading, use the directory settings and database settings in the cluster properties file of your current version to form the basis of your new cluster properties file.

Using the existing HDP cluster properties file, make the following changes:

  • Upgrading from HDP 1.3 to HDP 2.2:

    1. Change JOBTRACKER_HOST to RESOURCEMANAGER_HOST (leave the definition the same).

    2. (Optional:)Add a definition for CLIENT_HOSTS.

    3. (Optional:) Add a definition for KNOX_HOST.

    4. (Optional:) Add a definition for STORM_NIMBUS.

    5. (Optional:) Add a definition for STORM_SUPERVISORS.

    6. (Optional:) Add a definition for FALCON_HOSTS.

    7. If you are upgrading a High Availability cluster, change HA_NAMENODE_HOST to NN_HA_STANDBY_NAMENODE_HOST.

    8. Add a definition for DB_PORT. (Default port for derby is1527.)

    9. (Required) Add a definition for IS_TEZ.

    10. (Required) Add a definition for IS_PHOENIX.

    11. (Required) Add a definition for HDFS_NAMENODE_DATA_DIR. (Default is c:\hdpdata\hdfs.)

    12. (Required) Add a definition for HDFS_DATANODE_DATA_DIR. (Default is c:\hdpdata\hdfs.)

    13. (Required) Add a definition for IS_HDFS_HA. (Default is "no".)

    14. (Required) If you are using msiexec to install HDP 2.2, there are two new mandatory parameters: RANGER (default = "no") and KNOX_MASTER_SECRET (user-supplied password). If you plan to use Ranger, see Manually Creating a Cluster Properties File for a list of Ranger properties.

  • Upgrading from HDP 2.0 to HDP 2.2:

    1. (Optional:) Add a definition for KNOX_HOST.

    2. (Optional:) Add a definition for STORM_NIMBUS.

    3. (Optional:) Add a definition for STORM_SUPERVISORS.

    4. (Optional:) Add a definition for FALCON_HOSTS.

    5. Add a definition for DB_PORT. (Default port for derby is 1527.)

    6. (Required) Add a definition for IS_TEZ.

    7. (Required) Add a definition for IS_PHOENIX.

    8. For High Availability clusters, update the HA properties as follows:

      1. Change HA_NAMENODE_HOST to NN_HA_STANDBY_NAMENODE_HOST.

      2. Change HA_JOURNALNODE_HOSTS to NN_HA_JOURNALNODE_HOSTS.

      3. Change HA_CLUSTER_NAME to NN_HA_CLUSTER_NAME.

      4. Change HA_JOURNALNODE_EDITS_DIR to NN_HA_JOURNALNODE_EDITS_DIR

    9. (Required) Add a definition for HDFS_NAMENODE_DATA_DIR. (Default is c:\hdpdata\hdfs.)

    10. (Required) Add a definition for HDFS_DATANODE_DATA_DIR. (Default is c:\hdpdata\hdfs.)

    11. (Required) Add a definition for IS_HDFS_HA. (Default is "No".)

    12. (Required) If you are using msiexec to install HDP 2.2, there are two new mandatory parameters: RANGER (default = "no") and KNOX_MASTER_SECRET (user-supplied password). If you plan to use Ranger, see Manually Creating a Cluster Properties File for a list of Ranger properties.

  • Upgrading from HDP 2.1 to HDP 2.2

    1. (Required) Add a definition for HDFS_NAMENODE_DATA_DIR. (Default is c:\hdpdata\hdfs.)

    2. (Required) Add a definition for HDFS_DATANODE_DATA_DIR. (Default is c:\hdpdata\hdfs.) Note that NameNode and DataNode service startup might fail if the new datanode and namenode directories do not have hadoop user permissions. This could happen if you restore HDFS metadata from a backup. To avoid this issue, add the original datanode/namenode path to the cluster properties file before upgrading.

    3. (Required) Add a definition for IS_HDFS_HA. (Default is "No".)

    4. (Required) If you are using msiexec to install HDP 2.2, there are two new mandatory parameters: RANGER (default = "no") and KNOX_MASTER_SECRET If you plan to use Ranger, see Manually Creating a Cluster Properties File for a list of Ranger properties.

Save the new cluster properties file for use with the installer.


loading table of contents...