Repository: incubator-impala Updated Branches: refs/heads/doc_prototype 0c0d34b86 -> 0fcb0b3fe
Clean up stray CDH 4 and minor oversights noticed during proofreading. Project: http://git-wip-us.apache.org/repos/asf/incubator-impala/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-impala/commit/0fcb0b3f Tree: http://git-wip-us.apache.org/repos/asf/incubator-impala/tree/0fcb0b3f Diff: http://git-wip-us.apache.org/repos/asf/incubator-impala/diff/0fcb0b3f Branch: refs/heads/doc_prototype Commit: 0fcb0b3fe767cc250e460b4b523475b051b7b588 Parents: 0c0d34b Author: John Russell <[email protected]> Authored: Wed Nov 2 15:22:36 2016 -0700 Committer: John Russell <[email protected]> Committed: Wed Nov 2 15:22:36 2016 -0700 ---------------------------------------------------------------------- docs/topics/impala_cm_installation.xml | 2 +- docs/topics/impala_config_performance.xml | 114 +------------------------ docs/topics/impala_create_table.xml | 2 +- docs/topics/impala_install.xml | 28 ------ docs/topics/impala_noncm_installation.xml | 8 +- docs/topics/impala_prereqs.xml | 2 +- 6 files changed, 6 insertions(+), 150 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/0fcb0b3f/docs/topics/impala_cm_installation.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_cm_installation.xml b/docs/topics/impala_cm_installation.xml index ff8325d..2cc2ac5 100644 --- a/docs/topics/impala_cm_installation.xml +++ b/docs/topics/impala_cm_installation.xml @@ -36,7 +36,7 @@ <p> For information on installing Impala in a Cloudera Manager-managed environment, see - <xref audience="integrated" href="cm_ig_install_impala.xml"/><xref audience="standalone" href="http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_install_impala.html"; scope="external" format="html"/>. + <xref audience="integrated" href="cm_ig_install_impala.xml"/><xref audience="standalone" href="http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_install_impala.html"; scope="external" format="html">Installing Impala</xref>. </p> <p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/0fcb0b3f/docs/topics/impala_config_performance.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_config_performance.xml b/docs/topics/impala_config_performance.xml index e1a004c..0a44a33 100644 --- a/docs/topics/impala_config_performance.xml +++ b/docs/topics/impala_config_performance.xml @@ -62,15 +62,8 @@ enable short-circuit reads through a checkbox in the user interface and that setting takes effect for Impala as well. </note> </p> - <p> Cloudera strongly recommends using Impala with CDH 4.2 or higher, - ideally the latest 4.x release. Impala does support short-circuit reads - with CDH 4.1, but for best performance, upgrade to CDH 4.3 or higher. - The process of configuring short-circuit reads varies according to which - version of CDH you are using. Choose the procedure that is appropriate - for your environment. </p> <p> - <b>To configure DataNodes for short-circuit reads with CDH 4.2 or - higher:</b> + <b>To configure DataNodes for short-circuit reads:</b> </p> <ol id="ol_qlq_wyv_ls"> <li id="copy_config_files"> Copy the client @@ -127,111 +120,6 @@ <li id="restart_all_datanodes"> After applying these changes, restart all DataNodes. </li> </ol> - <p> - <b>To configure DataNodes for short-circuit reads with CDH 4.1:</b> - </p> - <!-- Repeated twice, turn into a conref. --> - <note> Cloudera strongly recommends using Impala with CDH 4.2 or higher, - ideally the latest 4.x release. Impala does support short-circuit reads - with CDH 4.1, but for best performance, upgrade to CDH 4.3 or higher. - The process of configuring short-circuit reads varies according to which - version of CDH you are using. Choose the procedure that is appropriate - for your environment. </note> - <ol id="ol_cqq_wyv_ls"> - <li> Enable short-circuit reads by adding settings to the Impala - <codeph>core-site.xml</codeph> file. <ul id="ul_a5q_wyv_ls"> - <li> If you installed Impala using Cloudera Manager, short-circuit - reads should be properly configured, but you can review the - configuration by checking the contents of - the <codeph>core-site.xml</codeph> file, which is installed at - <codeph>/etc/impala/conf</codeph> by default. </li> - <li> If you installed using packages, instead of using Cloudera - Manager, create the <codeph>core-site.xml</codeph> file. This can - be easily done by copying - the <codeph>core-site.xml</codeph> client configuration file from - another machine that is running Hadoop services. This file must be - copied to the Impala configuration directory. The Impala - configuration directory is set by - the <codeph>IMPALA_CONF_DIR</codeph> environment variable and is - by default <codeph>/etc/impala/conf</codeph>. To confirm the - Impala configuration directory, check - the <codeph>IMPALA_CONF_DIR</codeph> environment variable value. - <note> If the Impala configuration directory does not exist, - create it and then add the <codeph>core-site.xml</codeph> file. - </note> - </li> - </ul> Add the following to the <codeph>core-site.xml</codeph> file: <codeblock><property> - <name>dfs.client.read.shortcircuit</name> -   <value>true</value> -</property></codeblock> - <note> For an installation managed by Cloudera Manager, specify these - settings in the Impala dialogs, in the options field for HDFS. <ph - conref="../shared/impala_common.xml#common/safety_valve" /> - </note> - </li> - <li> For each DataNode, enable access by adding the following to - the <codeph>hdfs-site.xml</codeph> file: <codeblock rev="1.3.0"><property> - <name>dfs.client.use.legacy.blockreader.local</name> - <value>true</value> -</property> - -<property> - <name>dfs.datanode.data.dir.perm</name> - <value>750</value> -</property> - -<property> - <name>dfs.block.local-path-access.user</name> - <value>impala</value> -</property> - -<property> - <name>dfs.client.file-block-storage-locations.timeout.millis</name> - <value>10000</value> -</property></codeblock> - <note> In the preceding example, - the <codeph>dfs.block.local-path-access.user</codeph> is the user - running the <codeph>impalad</codeph> process. By default, that - account is <codeph>impala</codeph>. </note> - </li> - <li> Use <codeph>usermod</codeph>  to add users requiring local block - access to the appropriate HDFS group. For example, if you - assigned <codeph>impala</codeph> to the - <codeph>dfs.block.local-path-access.user</codeph>  property, you - would add <codeph>impala</codeph>  to the hadoop HDFS group: <codeblock>$ usermod -a -G hadoop impala</codeblock> - <note> The default HDFS group is <codeph>hadoop</codeph>, but it is - possible to have an environment configured to use an alternate - group. To find the configured HDFS group name using the Cloudera - Manager Admin Console: <ol id="ol_km4_4bc_nr"> - <li>Go to the HDFS service.</li> - <!-- Formerly: conref="../shared/cm_common_elements.xml#cm/config_edit" --> - <li>Click the <uicontrol>Configuration</uicontrol> tab.</li> - <li>Click <menucascade> - <uicontrol>Scope</uicontrol> - <uicontrol><varname>HDFS service name</varname> - (Service-Wide)</uicontrol> - </menucascade>.</li> - <li>Click <menucascade> - <uicontrol>Category</uicontrol> - <uicontrol>Advanced</uicontrol> - </menucascade>.</li> - <li>The <uicontrol>Shared Hadoop Group Name</uicontrol> property - contains the group name.</li> - </ol></note> - <note> If you are going to enable block location tracking, you can - skip copying configuration files and restarting DataNodes and go - straight to <xref href="#config_performance/block_location_tracking"/>. - Configuring short-circuit reads and block - location tracking require the same process of copying files and - restarting services, so you can complete that process once when you - have completed all configuration changes. Whether you copy files and - restart services now or during configuring block location tracking, - short-circuit reads are not enabled until you complete those final - steps. </note> - </li> - <li conref="#config_performance/copy_config_files" /> - <li conref="#config_performance/restart_all_datanodes" /> - </ol> </section> <section id="block_location_tracking"> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/0fcb0b3f/docs/topics/impala_create_table.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_create_table.xml b/docs/topics/impala_create_table.xml index 26f99c4..1b5552f 100644 --- a/docs/topics/impala_create_table.xml +++ b/docs/topics/impala_create_table.xml @@ -23,7 +23,7 @@ <conbody> <p> - <indexterm audience="HTML">CREATE TABLE statement</indexterm> + <indexterm audience="Cloudera">CREATE TABLE statement</indexterm> Creates a new table and specifies its characteristics. While creating a table, you optionally specify aspects such as: </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/0fcb0b3f/docs/topics/impala_install.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_install.xml b/docs/topics/impala_install.xml index 452ed03..ab68314 100644 --- a/docs/topics/impala_install.xml +++ b/docs/topics/impala_install.xml @@ -103,32 +103,4 @@ </conbody> </concept> - <concept audience="standalone" id="install_cdh4"> - - <title>Impala Installation Procedure for CDH 4 Users</title> - - <conbody> - - <p> - You can install Impala under CDH 4 in one of two ways: - </p> - - <ul> - <li> - Using the Cloudera Manager installer. This is the recommended technique for doing a reliable and verified - Impala installation. Cloudera Manager 4.8 or higher can automatically install, configure, manage, and - monitor Impala 1.2.1 and higher. The latest Cloudera Manager is always preferable, because newer Cloudera - Manager releases have configuration settings for the most recent Impala features. - </li> - - <li> - Using a manual process for systems not managed by Cloudera Manager. You must do additional verification - steps in this case, to check that Impala can interact with other Hadoop components correctly, and that - your cluster is configured for efficient Impala execution. - </li> - </ul> - - <p outputclass="toc"/> - </conbody> - </concept> </concept> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/0fcb0b3f/docs/topics/impala_noncm_installation.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_noncm_installation.xml b/docs/topics/impala_noncm_installation.xml index 6a26cd3..deaca5d 100644 --- a/docs/topics/impala_noncm_installation.xml +++ b/docs/topics/impala_noncm_installation.xml @@ -41,8 +41,6 @@ <ol> <li> Install CDH as described in the Installation section of the - <xref href="http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html"; scope="external" format="html">CDH - 4 Installation Guide</xref> or the <!-- Original URL: http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/latest/CDH5-Installation-Guide/CDH5-Installation-Guide.html --> <xref href="http://www.cloudera.com/documentation/enterprise/latest/topics/installation.html"; scope="external" format="html">CDH 5 Installation Guide</xref>. @@ -51,8 +49,6 @@ <li> <p> Install the Hive metastore somewhere in your cluster, as described in the Hive Installation topic in the - <xref href="http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/cdh4ig_topic_18.html"; scope="external" format="html">CDH - 4 Installation Guide</xref> or the <!-- Original URL: http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/latest/CDH5-Installation-Guide/cdh_ig_hive_installation.html --> <xref href="http://www.cloudera.com/documentation/enterprise/latest/topics/cdh_ig_hive_installation.html"; scope="external" format="html">CDH 5 Installation Guide</xref>. As part of this process, you configure the Hive metastore to use an external @@ -61,7 +57,7 @@ described in the CDH Installation Guide). </p> <p> - <ph rev="upstream">Cloudera</ph> recommends setting up a Hive metastore service rather than connecting directly to the metastore + Cloudera recommends setting up a Hive metastore service rather than connecting directly to the metastore database; this configuration is required when running Impala under CDH 4.1. Make sure the <filepath>/etc/impala/conf/hive-site.xml</filepath> file contains the following setting, substituting the appropriate hostname for <varname>metastore_server_host</varname>: @@ -123,7 +119,7 @@ $ sudo apt-get install impala-state-store # Service start/stop script $ sudo apt-get install impala-catalog # Service start/stop script </codeblock> <note> - <ph rev="upstream">Cloudera</ph> recommends that you not install Impala on any HDFS NameNode. Installing Impala on NameNodes + Cloudera recommends that you not install Impala on any HDFS NameNode. Installing Impala on NameNodes provides no additional data locality, and executing queries with such a configuration might cause memory contention and negatively impact the HDFS NameNode. </note> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/0fcb0b3f/docs/topics/impala_prereqs.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_prereqs.xml b/docs/topics/impala_prereqs.xml index 0587c6f..88b7265 100644 --- a/docs/topics/impala_prereqs.xml +++ b/docs/topics/impala_prereqs.xml @@ -234,7 +234,7 @@ in a message of the form: </p> -<codeblock>Using hostname: impala-daemon-1.cloudera.com</codeblock> +<codeblock>Using hostname: impala-daemon-1.example.com</codeblock> <p> In the majority of cases, this automatic detection works correctly. If you need to explicitly set the
