Repository: incubator-impala Updated Branches: refs/heads/master 0ad55ba5a -> 545bfcfe6
IMPALA-3401 [DOCS] Phase 5 of "Cloudera Manager" removal. Most of these fixes entailed hiding the paragraph where there are mentions of CM and writing a replacement paragraph for the upstream docs. This removes the CM references from the rendered docs. A subsequent cleanup project will remove occurrences of CM from the XML. This patch includes fixes to files in response to John Russell's first set of review comments. Change-Id: I4967fae275a8822274aece14a15107237445aba5 Reviewed-on: http://gerrit.cloudera.org:8080/6070 Reviewed-by: John Russell <[email protected]> Tested-by: Impala Public Jenkins Project: http://git-wip-us.apache.org/repos/asf/incubator-impala/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-impala/commit/b48bdaa9 Tree: http://git-wip-us.apache.org/repos/asf/incubator-impala/tree/b48bdaa9 Diff: http://git-wip-us.apache.org/repos/asf/incubator-impala/diff/b48bdaa9 Branch: refs/heads/master Commit: b48bdaa9b7a519a6750d8a97855e8fd5136a8846 Parents: 0ad55ba Author: Laurel Hale <[email protected]> Authored: Fri Feb 17 22:24:27 2017 -0800 Committer: Impala Public Jenkins <[email protected]> Committed: Thu Mar 2 23:01:10 2017 +0000 ---------------------------------------------------------------------- docs/topics/impala_isilon.xml | 8 +++----- docs/topics/impala_logging.xml | 23 +++++++++++------------ docs/topics/impala_s3.xml | 7 +++++++ docs/topics/impala_webui.xml | 24 ++++++++++++++---------- 4 files changed, 35 insertions(+), 27 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/b48bdaa9/docs/topics/impala_isilon.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_isilon.xml b/docs/topics/impala_isilon.xml index 12e6343..f475ae8 100644 --- a/docs/topics/impala_isilon.xml +++ b/docs/topics/impala_isilon.xml @@ -87,7 +87,7 @@ CREATE TABLE d1.t2 (a TINYINT, b BOOLEAN); the temporary data for the spill-to-disk feature, that configuration is not recommended due to the need to transfer the data both ways using remote I/O. </p> - + <p> When tuning Impala queries on HDFS, you typically try to avoid any remote reads. When the data resides on Isilon storage, all the I/O consists of remote reads. @@ -96,10 +96,8 @@ CREATE TABLE d1.t2 (a TINYINT, b BOOLEAN); primarily convenience of not having to move or copy large volumes of data to HDFS, rather than raw query performance. You can increase the performance of Impala I/O for Isilon systems by increasing the value for the - <codeph>num_remote_hdfs_io_threads</codeph> configuration parameter, - in the Cloudera Manager user interface for clusters using Cloudera Manager, - or through the <codeph>--num_remote_hdfs_io_threads</codeph> startup option - for the <cmdname>impalad</cmdname> daemon on clusters not using Cloudera Manager. + <codeph>--num_remote_hdfs_io_threads</codeph> startup option for the + <cmdname>impalad</cmdname> daemon. </p> <!-- <p outputclass="toc inpage"/> --> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/b48bdaa9/docs/topics/impala_logging.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_logging.xml b/docs/topics/impala_logging.xml index 79bc112..d209c27 100644 --- a/docs/topics/impala_logging.xml +++ b/docs/topics/impala_logging.xml @@ -185,8 +185,7 @@ under the License. <conbody> <p> - If you are using Impala in an environment not managed by Cloudera Manager, review Impala log files on each - host, when you have traced an issue back to a specific system. + Review Impala log files on each host, when you have traced an issue back to a specific system. </p> </conbody> @@ -359,13 +358,14 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we <title>Setting Logging Levels</title> <conbody> - + <p> - Impala uses the GLOG system, which supports three logging levels. You can adjust the logging levels using - the Cloudera Manager Admin Console. You can adjust logging levels without going through the Cloudera - Manager Admin Console by exporting variable settings. To change logging settings manually, use a command + Impala uses the GLOG system, which supports three logging levels. You can adjust logging levels + by exporting variable settings. To change logging settings manually, use a command similar to the following on each node before starting <codeph>impalad</codeph>: </p> + + <codeblock>export GLOG_v=1</codeblock> @@ -438,13 +438,12 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we <p> <indexterm audience="hidden">redaction</indexterm> <term>Log redaction</term> is a security feature that prevents sensitive information from being displayed in - locations used by administrators for monitoring and troubleshooting, such as log files, the Cloudera Manager - user interface, and the Impala debug web user interface. You configure regular expressions that match - sensitive types of information processed by your system, such as credit card numbers or tax IDs, and literals - matching these patterns are obfuscated wherever they would normally be recorded in log files or displayed in - administration or debugging user interfaces. + locations used by administrators for monitoring and troubleshooting, such as log files and the Impala debug web + user interface. You configure regular expressions that match sensitive types of information processed by your + system, such as credit card numbers or tax IDs, and literals matching these patterns are obfuscated wherever + they would normally be recorded in log files or displayed in administration or debugging user interfaces. </p> - + <p> In a security context, the log redaction feature is complementary to the Sentry authorization framework. Sentry prevents unauthorized users from being able to directly access table data. Redaction prevents http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/b48bdaa9/docs/topics/impala_s3.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_s3.xml b/docs/topics/impala_s3.xml index 5a3dcf4..617154c 100644 --- a/docs/topics/impala_s3.xml +++ b/docs/topics/impala_s3.xml @@ -148,6 +148,13 @@ under the License. </codeblock> <p> + After specifying the credentials, restart both the Impala and + Hive services. (Restarting Hive is required because Impala queries, CREATE TABLE statements, and so on go + through the Hive metastore.) + </p> + + + <p audience="hidden"> As of CDH 5.8, these settings do not have corresponding controls in the Cloudera Manager user interface. Specify them in the <uicontrol>HDFS Client Advanced Configuration Snippet (Safety Valve) for core-site.xml</uicontrol> field. After specifying the credentials, restart both the Impala and Hive http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/b48bdaa9/docs/topics/impala_webui.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_webui.xml b/docs/topics/impala_webui.xml index 176822a..60627e9 100644 --- a/docs/topics/impala_webui.xml +++ b/docs/topics/impala_webui.xml @@ -51,9 +51,7 @@ under the License. statements from <cmdname>impala-shell</cmdname>. Each host that runs the <cmdname>impalad</cmdname> daemon has its own instance of the web UI, with details about those queries for which that - host served as the coordinator. To get a consolidated view for all queries, - it is usually more convenient to use the charts, graphs, and other monitoring - features in Cloudera Manager. The <cmdname>impalad</cmdname> web UI is mainly + host served as the coordinator. The <cmdname>impalad</cmdname> web UI is mainly for diagnosing query problems that can be traced to a particular node. </p> </li> @@ -78,15 +76,14 @@ under the License. </li> </ul> </p> - + <note> <p> The web user interface is primarily for problem diagnosis and troubleshooting. The items listed and their - formats are subject to change. To monitor Impala health, particularly across the entire cluster at once, use - the Cloudera Manager interface. + formats are subject to change. </p> </note> - + <p outputclass="toc inpage"/> </conbody> @@ -194,14 +191,15 @@ under the License. <codeph>http://<varname>impala-server-hostname</varname>:25000/logs</codeph> (non-secure cluster) or <codeph>https://<varname>impala-server-hostname</varname>:25000/logs</codeph> (secure cluster). </p> - + <p> This page shows the last portion of the <filepath>impalad.INFO</filepath> log file, the most detailed of the info, warning, and error logs for the <cmdname>impalad</cmdname> daemon. You can refer here to see the details of the most recent operations, whether the operations succeeded or encountered errors. This central page can be more convenient than looking around the filesystem for the log files, which could be - in different locations on clusters that use Cloudera Manager or not. + in different locations on clusters that use cluster management software. </p> + </conbody> </concept> @@ -236,9 +234,15 @@ under the License. <codeph>http://<varname>impala-server-hostname</varname>:25000/metrics</codeph> (non-secure cluster) or <codeph>https://<varname>impala-server-hostname</varname>:25000/metrics</codeph> (secure cluster). </p> - + <p> This page displays the current set of metrics: counters and flags representing various aspects of + <cmdname>impalad</cmdname> internal operation. + </p> + + + <p audience="hidden"> + This page displays the current set of metrics: counters and flags representing various aspects of <cmdname>impalad</cmdname> internal operation. For the meanings of these metrics, see <xref href="http://www.cloudera.com/documentation/enterprise/latest/topics/cm_metrics_impala.html"; scope="external" format="html">Impala Metrics</xref> in the Cloudera Manager documentation.
