Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8FD06200C02 for ; Fri, 6 Jan 2017 00:59:53 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8E686160B42; Thu, 5 Jan 2017 23:59:53 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3F026160B33 for ; Fri, 6 Jan 2017 00:59:52 +0100 (CET) Received: (qmail 21765 invoked by uid 500); 5 Jan 2017 23:59:51 -0000 Mailing-List: contact commits-help@impala.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@impala.incubator.apache.org Delivered-To: mailing list commits@impala.incubator.apache.org Received: (qmail 21756 invoked by uid 99); 5 Jan 2017 23:59:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jan 2017 23:59:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 0233C18014B for ; Thu, 5 Jan 2017 23:59:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -6.218 X-Spam-Level: X-Spam-Status: No, score=-6.218 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id iXYECtIT7lCy for ; Thu, 5 Jan 2017 23:59:46 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id E73835F613 for ; Thu, 5 Jan 2017 23:59:44 +0000 (UTC) Received: (qmail 21572 invoked by uid 99); 5 Jan 2017 23:59:44 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jan 2017 23:59:44 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 00AD9DFC3F; Thu, 5 Jan 2017 23:59:43 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: jrussell@apache.org To: commits@impala.incubator.apache.org Date: Thu, 05 Jan 2017 23:59:46 -0000 Message-Id: <431c81064c424572ad11921767feb4a5@git.apache.org> In-Reply-To: <2e095e49398b46328ae4a427d46114c5@git.apache.org> References: <2e095e49398b46328ae4a427d46114c5@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [4/4] incubator-impala git commit: IMPALA-3401: Suppress blocks of content devoted to Cloudera Manager. archived-at: Thu, 05 Jan 2017 23:59:53 -0000 IMPALA-3401: Suppress blocks of content devoted to Cloudera Manager. Initial experiment to see how the doc looks & builds when the biggest, most obvious pieces of Cloudera Manager-related content are suppressed: - Primarily entire subtopics. - In some cases, individual notes, paragraphs, and list items. - Also the CM reference in the reused "cancel" text which showed up many times throughout the SQL syntax section. Just hiding in the output for now, rather than removing from source, because we might find there's generic material we need to hoist out of the CM-related subtopics. Was planning to use audience="hidden" to hide, but since that CR hasn't landed in master yet, still using audience="Cloudera" for the moment, and will switch attribute values later. A little rewording of titles and suppressing smaller elements such as paragraphs where the CM aspect didn't apply to the entire subtopic. Change-Id: Ic799f77bc758a1cf40c53fa412bf02d852901a69 Reviewed-on: http://gerrit.cloudera.org:8080/5607 Reviewed-by: Jim Apple Tested-by: John Russell Project: http://git-wip-us.apache.org/repos/asf/incubator-impala/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-impala/commit/c4ee03a7 Tree: http://git-wip-us.apache.org/repos/asf/incubator-impala/tree/c4ee03a7 Diff: http://git-wip-us.apache.org/repos/asf/incubator-impala/diff/c4ee03a7 Branch: refs/heads/master Commit: c4ee03a7e595e38886e6688182338a933a391285 Parents: 81c3653 Author: John Russell Authored: Sun Dec 18 13:17:16 2016 -0800 Committer: John Russell Committed: Thu Jan 5 23:55:45 2017 +0000 ---------------------------------------------------------------------- docs/impala.ditamap | 4 ++-- docs/shared/impala_common.xml | 16 +++++++--------- docs/topics/impala_admission.xml | 4 ++-- docs/topics/impala_authorization.xml | 4 ++-- docs/topics/impala_breakpad.xml | 2 +- docs/topics/impala_cm_installation.xml | 2 +- docs/topics/impala_config_options.xml | 4 ++-- docs/topics/impala_faq.xml | 8 ++++---- docs/topics/impala_hbase.xml | 2 +- docs/topics/impala_incompatible_changes.xml | 4 ++-- docs/topics/impala_isilon.xml | 4 ++-- docs/topics/impala_ldap.xml | 5 ++++- docs/topics/impala_logging.xml | 8 ++++---- docs/topics/impala_perf_hdfs_caching.xml | 4 ++-- docs/topics/impala_processes.xml | 2 +- docs/topics/impala_proxy.xml | 10 +++++----- docs/topics/impala_scalability.xml | 2 +- docs/topics/impala_ssl.xml | 2 +- docs/topics/impala_txtfile.xml | 4 ++-- docs/topics/impala_upgrading.xml | 8 ++++---- docs/topics/impala_webui.xml | 2 +- 21 files changed, 51 insertions(+), 50 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/impala.ditamap ---------------------------------------------------------------------- diff --git a/docs/impala.ditamap b/docs/impala.ditamap index 0e2b03d..b3c008a 100644 --- a/docs/impala.ditamap +++ b/docs/impala.ditamap @@ -714,8 +714,8 @@ https://issues.cloudera.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=p - - + + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/shared/impala_common.xml ---------------------------------------------------------------------- diff --git a/docs/shared/impala_common.xml b/docs/shared/impala_common.xml index 6783f43..8990dbb 100644 --- a/docs/shared/impala_common.xml +++ b/docs/shared/impala_common.xml @@ -576,7 +576,7 @@ under the License. in the impalad and catalogdconfiguration settings.

-
  • +

  • For clusters managed by Cloudera Manager, select the Use HDFS Rules to Map Kerberos Principals to Short Names @@ -605,7 +605,7 @@ under the License. Sentry logs all facts that lead up to authorization decisions at the debug level. If you do not understand why Sentry is denying access, the best way to debug is to temporarily turn on debug logging:

      -
    • +
    • In Cloudera Manager, add log4j.logger.org.apache.sentry=DEBUG to the logging settings for your service through the corresponding Logging Safety Valve field for the Impala, Hive Server 2, or Solr Server services. @@ -2356,8 +2356,7 @@ flight_num: INT32 SNAPPY DO:83456393 FPO:83488603 SZ:10216514/11474301

      Cancellation: Can be cancelled. To cancel this statement, use Ctrl-C from the impala-shell interpreter, the Cancel button from the - Watch page in Hue, Actions > Cancel from the - Queries list in Cloudera Manager, or Cancel from the list of + Watch page in Hue, or Cancel from the list of in-flight queries (for a particular node) on the Queries tab in the Impala web UI (port 25000).

      @@ -2367,8 +2366,7 @@ flight_num: INT32 SNAPPY DO:83456393 FPO:83488603 SZ:10216514/11474301 COMPUTE STATS) can be cancelled during some stages, when running INSERT or SELECT operations internally. To cancel this statement, use Ctrl-C from the impala-shell interpreter, the Cancel button from the - Watch page in Hue, Actions > Cancel from the - Queries list in Cloudera Manager, or Cancel from the list of + Watch page in Hue, or Cancel from the list of in-flight queries (for a particular node) on the Queries tab in the Impala web UI (port 25000).

      @@ -3126,7 +3124,7 @@ select * from header_line limit 10; Other security settings may prevent Impala from writing core dumps even when this option is enabled.

      • -
    • +

    • On systems managed by Cloudera Manager, the default location for core dumps is on a temporary filesystem, which can lead to out-of-space issues if the core dumps are large, frequent, or @@ -3189,7 +3187,7 @@ sudo pip-python install ssl SYNC_DDL query option. -

      +

      In a Cloudera Manager environment, the catalog service is not recognized or managed by Cloudera Manager versions prior to 4.8. Cloudera Manager 4.8 and higher require the catalog service to be present for Impala. Therefore, if you upgrade to Cloudera Manager 4.8 or higher, you must also upgrade Impala to 1.2.1 @@ -3658,7 +3656,7 @@ sudo pip-python install ssl JAVA_TOOL_OPTIONS="-Xmx8g"

      • -
    • +

    • On systems managed by Cloudera Manager, include this value in the configuration field Java Heap Size of Catalog Server in Bytes (Cloudera Manager 5.7 and higher), or http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_admission.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_admission.xml b/docs/topics/impala_admission.xml index 51f1fbf..0c55e69 100644 --- a/docs/topics/impala_admission.xml +++ b/docs/topics/impala_admission.xml @@ -606,7 +606,7 @@ under the License. - + @@ -708,7 +708,7 @@ impala.admission-control.pool-queue-timeout-ms.queue_name -

      +
      Example Admission Control Configurations Using Cloudera Manager http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_authorization.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_authorization.xml b/docs/topics/impala_authorization.xml index 646b8d2..a844ac3 100644 --- a/docs/topics/impala_authorization.xml +++ b/docs/topics/impala_authorization.xml @@ -222,7 +222,7 @@ under the License.

        -
      • +

      • In an environment managed by Cloudera Manager, the server name is specified through Impala (Service-Wide)CategoryAdvancedSentry Service and @@ -1586,7 +1586,7 @@ column-level security was by creating views that referenced particular sets of c - + Managing Sentry for Impala through Cloudera Manager http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_breakpad.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_breakpad.xml b/docs/topics/impala_breakpad.xml index 79e491c..b437da3 100644 --- a/docs/topics/impala_breakpad.xml +++ b/docs/topics/impala_breakpad.xml @@ -85,7 +85,7 @@ under the License.

          -
        • +

        • Clusters managed by Cloudera Manager: /var/log/impala-minidumps/daemon_name

          http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_cm_installation.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_cm_installation.xml b/docs/topics/impala_cm_installation.xml index 7a4ad60..a7aea7b 100644 --- a/docs/topics/impala_cm_installation.xml +++ b/docs/topics/impala_cm_installation.xml @@ -18,7 +18,7 @@ specific language governing permissions and limitations under the License. --> - + Installing Impala with Cloudera Manager http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_config_options.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_config_options.xml b/docs/topics/impala_config_options.xml index 1346fe3..bc91f9d 100644 --- a/docs/topics/impala_config_options.xml +++ b/docs/topics/impala_config_options.xml @@ -66,7 +66,7 @@ under the License. - + Configuring Impala Startup Options through Cloudera Manager @@ -243,7 +243,7 @@ Starting Impala Catalog Server: [ OK ] to:

          export ENABLE_CORE_DUMPS=${ENABLE_COREDUMPS:-true} -

          +

          On systems managed by Cloudera Manager, enable the Enable Core Dump setting for the Impala service.

          http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_faq.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_faq.xml b/docs/topics/impala_faq.xml index a3fb3cd..6988b8d 100644 --- a/docs/topics/impala_faq.xml +++ b/docs/topics/impala_faq.xml @@ -52,7 +52,7 @@ under the License. FAQs in this category:

          -
          +
          How do I try Impala out? @@ -73,7 +73,7 @@ under the License.
          -
          +
          Does Cloudera offer a VM for demonstrating Impala? @@ -409,7 +409,7 @@ through the DEFAULT_ORDER_BY_LIMIT query option.
          - What processor type and speed does Cloudera recommend? + What processor type and speed work best for Impala? @@ -473,7 +473,7 @@ through the DEFAULT_ORDER_BY_LIMIT query option. information about Impala performance optimizations and tuning techniques for queries.
          • -
        • +
        • Using Cloudera Manager, you can deploy and manage your Impala services. Cloudera Manager is the best way to get started with Impala on your cluster.
          • http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_hbase.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_hbase.xml b/docs/topics/impala_hbase.xml index 4cb3344..6f7daf3 100644 --- a/docs/topics/impala_hbase.xml +++ b/docs/topics/impala_hbase.xml @@ -162,7 +162,7 @@ under the License. </property> -

          +

          Currently, Cloudera Manager does not have an Impala-only override for HBase settings, so any HBase configuration change you make through Cloudera Manager would take affect for all HBase applications. Therefore, this change is not recommended on systems managed by Cloudera Manager. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_incompatible_changes.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_incompatible_changes.xml b/docs/topics/impala_incompatible_changes.xml index 52be2af..9fad426 100644 --- a/docs/topics/impala_incompatible_changes.xml +++ b/docs/topics/impala_incompatible_changes.xml @@ -1276,7 +1276,7 @@ select * from `cross`; to Impala 1.2.x in general.

          -

          +

          @@ -1318,7 +1318,7 @@ select * from `cross`;

        -

        +

        http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_isilon.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_isilon.xml b/docs/topics/impala_isilon.xml index 9bc426d..8de8e4f 100644 --- a/docs/topics/impala_isilon.xml +++ b/docs/topics/impala_isilon.xml @@ -103,7 +103,7 @@ CREATE TABLE d1.t2 (a TINYINT, b BOOLEAN); for the impalad daemon on clusters not using Cloudera Manager.

        -

        +

        - + Required Configurations

        Specify the following configurations in Cloudera Manager on the ClustersIsilon ServiceConfiguration tab:

          http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_ldap.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_ldap.xml b/docs/topics/impala_ldap.xml index 343d547..3100088 100644 --- a/docs/topics/impala_ldap.xml +++ b/docs/topics/impala_ldap.xml @@ -187,6 +187,9 @@ under the License.

          For clusters not managed by Cloudera Manager, specify the option on the impalad command line. +

          + +

          For clusters managed by Cloudera Manager 5.4.0 and higher, search for the configuration field names ldap_domain, ldap_basedn, or ldap_bind_pattern, @@ -300,7 +303,7 @@ username, for example username@example.com. -

          +
          Enabling LDAP for Impala in Hue Using Cloudera Manager

            http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_logging.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_logging.xml b/docs/topics/impala_logging.xml index dbbea4b..40399ef 100644 --- a/docs/topics/impala_logging.xml +++ b/docs/topics/impala_logging.xml @@ -167,7 +167,7 @@ under the License. immediately. -
          1. +
          2. Cloudera Manager has an Impala configuration setting that sets the -logbuflevel startup option.
            3. @@ -179,7 +179,7 @@ under the License. - Managing Impala Logs through Cloudera Manager or Manually + Managing Impala Logs @@ -189,7 +189,7 @@ under the License. -

            +

            Cloudera recommends installing Impala through the Cloudera Manager administration interface. To assist with troubleshooting, Cloudera Manager collects front-end and back-end logs together into a single view, and let you do a search across log data for all the managed nodes rather than examining the logs on each node @@ -250,7 +250,7 @@ under the License. Linux tool or technique of choice. A value of 1 preserves only the very latest log file.

            -

            +

            To set up log rotation on a system managed by Cloudera Manager 5.4.0 and higher, search for the max_log_files option name and set the appropriate value for the Maximum Log Files field for each Impala configuration category (Impala, Catalog Server, and StateStore). http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_perf_hdfs_caching.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_perf_hdfs_caching.xml b/docs/topics/impala_perf_hdfs_caching.xml index c8f168c..017c436 100644 --- a/docs/topics/impala_perf_hdfs_caching.xml +++ b/docs/topics/impala_perf_hdfs_caching.xml @@ -469,11 +469,11 @@ Found 122 entries

        -

        +

        Cloudera Manager:

        -
          +
          • You can enable or disable HDFS caching through Cloudera Manager, using the configuration setting Maximum Memory Used for Caching for the HDFS service. This control sets the HDFS http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_processes.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_processes.xml b/docs/topics/impala_processes.xml index 0a54823..6bba031 100644 --- a/docs/topics/impala_processes.xml +++ b/docs/topics/impala_processes.xml @@ -69,7 +69,7 @@ under the License.

            - + Starting Impala through Cloudera Manager http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_proxy.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_proxy.xml b/docs/topics/impala_proxy.xml index c225cce..f064961 100644 --- a/docs/topics/impala_proxy.xml +++ b/docs/topics/impala_proxy.xml @@ -143,7 +143,7 @@ under the License. Run the load-balancing proxy server, pointing it at the configuration file that you set up.

            • -
          • +
          • On systems managed by Cloudera Manager, on the page ImpalaConfigurationImpala Daemon Default Group, specify a value for the Impala Daemons Load @@ -269,7 +269,7 @@ under the License. running the impalad daemon.
            • -
          • +
          • For a cluster managed by Cloudera Manager (5.4.2 or higher), fill in the Impala configuration setting Impala Daemons Load Balancer with the appropriate host:port combination. Then restart the Impala service. @@ -320,7 +320,7 @@ under the License. configuration snippet, add: --principal=impala/proxy_host@realm --be_principal=impala/actual_host@realm --keytab_file=path_to_merged_keytab - +

            On a cluster managed by Cloudera Manager 5.1 (or higher), when you set up Kerberos authentication using the wizard, you can choose to allow Cloudera Manager to deploy the @@ -335,7 +335,7 @@ under the License.

            • -
          • +
          • On a cluster managed by Cloudera Manager, create a role group to set the configuration values from the preceding step on a per-host basis.
            • @@ -352,7 +352,7 @@ under the License. Restart Impala to make the changes take effect. Follow the appropriate steps depending on whether you use Cloudera Manager or not:
              -
            • +
            • On a cluster managed by Cloudera Manager, restart the Impala service.
              • http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_scalability.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_scalability.xml b/docs/topics/impala_scalability.xml index ca567ea..69bd08f 100644 --- a/docs/topics/impala_scalability.xml +++ b/docs/topics/impala_scalability.xml @@ -469,7 +469,7 @@ Memory Usage: Additional Notes query. -
            • +
            • The Impala Queries dialog in Cloudera Manager. You can see the peak memory usage for a query, combined across all nodes in the cluster.
              • http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_ssl.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_ssl.xml b/docs/topics/impala_ssl.xml index 3efd1d3..7375cfd 100644 --- a/docs/topics/impala_ssl.xml +++ b/docs/topics/impala_ssl.xml @@ -56,7 +56,7 @@ under the License. - + Using Cloudera Manager http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_txtfile.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_txtfile.xml b/docs/topics/impala_txtfile.xml index 0b81ca9..f23d4d7 100644 --- a/docs/topics/impala_txtfile.xml +++ b/docs/topics/impala_txtfile.xml @@ -483,11 +483,11 @@ INSERT INTO csv SELECT * FROM other_file_format_table;
              1. Prepare your systems to work with LZO by downloading and installing the appropriate libraries: -

                +

                On systems managed by Cloudera Manager using parcels:

                -

                +

                See the setup instructions for the LZO parcel in the Cloudera Manager documentation for Cloudera Manager 5. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_upgrading.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_upgrading.xml b/docs/topics/impala_upgrading.xml index 837330b..3fea37b 100644 --- a/docs/topics/impala_upgrading.xml +++ b/docs/topics/impala_upgrading.xml @@ -47,7 +47,7 @@ under the License. upgrade from CDH 4 to the latest CDH 5, which also has the latest Impala.

                2. -
              2. +
              3. When you upgrade Impala, also upgrade Cloudera Manager if necessary:
                • @@ -92,7 +92,7 @@ under the License.

                  - + Upgrading Impala through Cloudera Manager - Parcels @@ -170,7 +170,7 @@ sudo apt-get purge pkg_names # Ubuntu, Debian - + Upgrading Impala through Cloudera Manager - Packages @@ -253,7 +253,7 @@ $ sudo apt-get install hadoop-lzo-cdh4 # Optional; if this package is already in - + Upgrading Impala without Cloudera Manager http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ee03a7/docs/topics/impala_webui.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_webui.xml b/docs/topics/impala_webui.xml index c90d812..612b882 100644 --- a/docs/topics/impala_webui.xml +++ b/docs/topics/impala_webui.xml @@ -104,7 +104,7 @@ under the License. suspect is having problems.

                  - + To get a convenient picture of the health of all Impala nodes in a cluster, use the Cloudera Manager interface, which collects the low-level operational information from all Impala nodes, and presents a unified view of the entire cluster.