You can define the cluster properties using the HDP Setup form. After you set the cluster property fields, you can then either export the configuration and use it deploy HDP from the command line, or you can complete the form and .
Open the command prompt and enter the following command:
runas /user:adminstrator msiexec /i "hdp-2.1.1.0.winpkg.msi" MSIUSEREALADMINDETECTION=1
The HDP Setup form displays.
Choose the type of deployment by selecting:
Configure Single Node: To install all cluster nodes on the current host; the hostname fields are pre-populated with the name of the current computer, see Quick Start Guide for Single Node Installation.
Configure Multi Node: To create a property file for cluster deployment or to manually install a node (or subset of nodes) on the current computer.
Set the fields in the required components:
Configuration Values for HDP Setup form
Configuration Property Name Description Example value Mandatory/ Optional/ Conditional HDP directory HDP installation directory. d:\hdp
Mandatory Log directory HDP's operational logs are written to this directory on each cluster host. Ensure that you have sufficient disk space for storing these log files. d:\hadoop\logs
Mandatory Data Directory HDP data will be stored in this directory on each cluster node. You can add multiple comma-separated data locations for multiple data directories. d:\hdp\data
Mandatory Enable LZO codec Use LZO compression for HDP. Selected Optional Use Tez in Hive Install Tez on the Hive host. Selected Optional NameNode Host The FQDN for the cluster node that will run the NameNode master service. NAMENODE_MASTER.acme.com
Mandatory Secondary NameNode Host[a] The FQDN for the cluster node that will run the Secondary NameNode master service. SECONDARY_NN_MASTER.acme.com
Mandatory/NA ResourceManager Host The FQDN for the cluster node that will run the YARN Resource Manager master service. RESOURCE_MANAGER.acme.com
Mandatory Hive Server Host The FQDN for the cluster node that will run the Hive Server master service. HIVE_SERVER_MASTER.acme.com
Mandatory Oozie Server Host The FQDN for the cluster node that will run the Oozie Server master service. OOZIE_SERVER_MASTER.acme.com
Mandatory WebHcat Host The FQDN for the cluster node that will run the WebHCat master service. WEBHCAT_MASTER.acme.com
Mandatory Slave hosts A comma-separated list of FQDN for those cluster nodes that will run the DataNode and TaskTracker services. slave1.acme.com, slave2.acme.com, slave3.acme.com
Mandatory Clients Hosts A comma-separated list of FQDN for those cluster nodes that will store JARs and other job related files. client.acme.com, client1.acme.com, client2.acme.com
Optional ZooKeeper hosts A comma-separated list of FQDN for those cluster nodes that will run the ZooKeeper hosts. ZOOKEEEPER-HOST.acme.com
Mandatory [a] Not applicable with HA.
Click install optional components, and complete the following fields:
Configuration Property Name Description Example value Mandatory/ Optional/ Conditional Install Phoenix Installs Phoenix on the HBase Server. Selected Optional Install Knox Installs Knox Gateway. Selected Optional Knox Master secret Enter the password for starting and stopping the gateway. knox-secret
Mandatory HBase Master host The FQDN for the cluster node that will run the HBase master. HBASE-MASTER.acme.com
Mandatory Falcon host The FQDN for the cluster node that will run Falcon. falcon-host.acme.com
Storm nimbus host The FQDN for the cluster node that will run the Storm Nimbus master service. storm-host.acme.com
Optional Knox host The FQDN for the cluster node that will run Knox. knox-host.acme.com
Mandatory Flume hosts A comma-separated list of FQDN for those cluster nodes that will run the Flume service. FLUME_SERVICE1.acme.com, FLUME_SERVICE2.acme.com, FLUME_SERVICE3.acme.com
Mandatory HBase Region Server hosts A comma-separated list of FQDN for those cluster nodes that will run the HBase Region Server services. slave1.acme.com, slave2.acme.com, slave3.acme.com
Mandatory Hive DB Name Database for Hive metastore. If using SQL Server, ensure that you create the database on the SQL Server instance. hivedb
Mandatory Storm supervisor hosts A comma-separated list of FQDN for those cluster nodes that will run the Storm Supervisors. storm-sup-host.acme.com
Optional Enter the database information for Hive and Oozie as follows:
Configuration Property Name Description Example value Mandatory/ Optional/ Conditional Hive DB Username User account credentials for Hive metastore database instance. Ensure that this user account has appropriate permissions. hive_user
Mandatory Hive DB Password hive_pass
Mandatory Oozie DB Name Database for Oozie metastore. If using SQL Server, ensure that you create the database on the SQL Server instance. ooziedb
Mandatory Oozie DB Username User account credentials for Oozie metastore database instance. Ensure that this user account has appropriate permissions. oozie_user
Mandatory Oozie DB Password oozie_pass
Mandatory DB Flavor Database type for Hive and Oozie metastores (allowed databases are SQL Server and Derby). To use default embedded Derby instance, set the value of this property to derby
. To use an existing SQL Server instance as the metastore DB, set the value asmssql
.mssql
orderby
Mandatory Database Hostname FQDN for the node where the metastore database service is installed. If using SQL Server, set the value to your SQL Server hostname. If using Derby for Hive metastore, set the value to HIVE_SERVER_HOST. sqlserver1.acme.com
Mandatory Database port This is an optional property required only if you are using SQL Server for Hive and Oozie metastores. By default, the database port is set to 1433
.1433 Optional To ensure that a multi-node cluster remains available, you should configure and enable High Availability. Configuring High Availability includes defining the locations and names of hosts in a cluster that are available to act as JournalNodes and the Resource Manager along with specifying a standby NameNode to fall back on in the event that the primary NameNode fails.
To configure NameNode High Availability, select the Enable Namenode HA check box, then enter values in the following fields:
High Availability Configuration Values for MSI Installer
Property Description Example Value Mandatory/ Optional Enable HA Whether to deploy a highly available NameNode or not. Selected Optional NN Journal Node Hosts A comma-separated list of FQDN for those cluster nodes that will run the JournalNode processes. journalnode1.acme.com, journalnode2.acme.com, journalnode3.acme.com
Optional NN HA Cluster Name This name is used for both configuration and authority component of absolute HDFS paths in the cluster. hdp2-ha-acme.com
Optional NN Journal Node Edits Directory This is the absolute path on the JournalNode machines where the edits and other local state used by the JournalNodes (JNs) are stored. You can only use a single path for this configuration. d:\hadoop\journal
Optional NN Standby Namenode Host The host for the standby NameNode. STANDBY_NAMENODE.acme.com Optional RM Cluster Name Logical name for the HA Resource Manager cluster. rmha-cluster
Optional RM Standby Host The host for the standby Resource Manager. STANDBY-resourcemgr.acme.com Optional Note To Enable High Availability, you must run several commands while starting cluster services.
To continue with the GUI installation process, select Install.
Note If you make a configuration mistake and want to clear fields, select Reset to clear all fields and begin again.
To export your HDP Setup configuration as a cluster properties text file and switch to the CLI installation process, select Export.
Note Selecting Export stops the GUI installation process and produces the
clusterproperties.txt
file based on your GUI fields. Verify that all information in the fields are accurate before proceeding.