Repository: incubator-hawq-docs Updated Branches: refs/heads/develop 8353b4c21 -> f1ffe58fb
Squashed commit of the following: commit 28216ddb50a0db01358002cf7fa15f8326b96186 Author: Jane Beckman <[email protected]> Date: Mon Nov 21 16:17:39 2016 -0800 Update links to Hortonworks docs Project: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/commit/f1ffe58f Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/f1ffe58f Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/f1ffe58f Branch: refs/heads/develop Commit: f1ffe58fb07ad60d6800bb6892e7a58ef8c29434 Parents: 8353b4c Author: David Yozie <[email protected]> Authored: Tue Nov 22 15:28:22 2016 -0800 Committer: David Yozie <[email protected]> Committed: Tue Nov 22 15:28:22 2016 -0800 ---------------------------------------------------------------------- admin/HAWQFilespacesandHighAvailabilityEnabledHDFS.html.md.erb | 2 +- install/select-hosts.html.md.erb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/f1ffe58f/admin/HAWQFilespacesandHighAvailabilityEnabledHDFS.html.md.erb ---------------------------------------------------------------------- diff --git a/admin/HAWQFilespacesandHighAvailabilityEnabledHDFS.html.md.erb b/admin/HAWQFilespacesandHighAvailabilityEnabledHDFS.html.md.erb index b725207..b4284be 100644 --- a/admin/HAWQFilespacesandHighAvailabilityEnabledHDFS.html.md.erb +++ b/admin/HAWQFilespacesandHighAvailabilityEnabledHDFS.html.md.erb @@ -20,7 +20,7 @@ To enable the HDFS NameNode HA feature for use with HAWQ, you need to perform th Enable high availability for NameNodes in your HDFS cluster. See the documentation for your Hadoop distribution for instructions on how to do this. -**Note:** If you're using Ambari to manage your HDFS cluster, you can use the Enable NameNode HA Wizard. For example, [this Hortonworks HDP procedure](https://docs.hortonworks.com/HDPDocuments/Ambari-2.2.1.1/bk_Ambari_Users_Guide/content/_how_to_configure_namenode_high_availability.html) outlines how to do this in Ambari for HDP. +**Note:** If you're using Ambari to manage your HDFS cluster, you can use the Enable NameNode HA Wizard. For example, [this Hortonworks HDP procedure](https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.1.0/bk_ambari-user-guide/content/how_to_configure_namenode_high_availability.html) outlines how to do this in Ambari for HDP. ### <a id="collectinginformationaboutthetargetfilespace"></a>Step 2: Collect Information about the Target Filespace http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/f1ffe58f/install/select-hosts.html.md.erb ---------------------------------------------------------------------- diff --git a/install/select-hosts.html.md.erb b/install/select-hosts.html.md.erb index c2fbdff..ecbe0b5 100644 --- a/install/select-hosts.html.md.erb +++ b/install/select-hosts.html.md.erb @@ -13,7 +13,7 @@ Complete this procedure for all HAWQ deployments: 2. **Choose the host machines that will run PXF.** Keep in mind these restrictions and requirements: - PXF must be installed on the HDFS NameNode *and* on all HDFS DataNodes. - If you have configured Hadoop with high availability, PXF must also be installed on all HDFS nodes including all NameNode services. - - If you want to use PXF with HBase or Hive, you must first install the HBase client \(hbase-client\) and/or Hive client \(hive-client\) on each machine where you intend to install PXF. See the [HDP installation documentation](http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.4/index.html) for more information. + - If you want to use PXF with HBase or Hive, you must first install the HBase client \(hbase-client\) and/or Hive client \(hive-client\) on each machine where you intend to install PXF. See the [HDP installation documentation](https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.0/index.html) for more information. 3. **Verify that required ports on all machines are unused.** By default, a HAWQ master or standby master service configuration uses port 5432. Hosts that run other PostgreSQL instances cannot be used to run a default HAWQ master or standby service configuration because the default PostgreSQL port \(5432\) conflicts with the default HAWQ port. You must either change the default port configuration of the running PostgreSQL instance or change the HAWQ master port setting during the HAWQ service installation to avoid port conflicts. **Note:** The Ambari server node uses PostgreSQL as the default metadata database. The Hive Metastore uses MySQL as the default metadata database. \ No newline at end of file
