You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by jr...@apache.org on 2017/03/13 19:12:02 UTC
incubator-impala git commit: IMPALA-3405: [DOCS] Pare down upgrading
section
Repository: incubator-impala
Updated Branches:
refs/heads/master 6441ca65b -> 5709b66e9
IMPALA-3405: [DOCS] Pare down upgrading section
Physically remove the CM upgrading instructions
and the yum, zypper, apt-get procedure too.
Replace with a reference to rebuilding and redeploying,
via instructions on the Apache Impala wiki.
Change-Id: I41f34772200b22d176cf41a7e7ecedc3f3904b6a
Reviewed-on: http://gerrit.cloudera.org:8080/6008
Tested-by: Impala Public Jenkins
Reviewed-by: John Russell <jr...@cloudera.com>
Project: http://git-wip-us.apache.org/repos/asf/incubator-impala/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-impala/commit/5709b66e
Tree: http://git-wip-us.apache.org/repos/asf/incubator-impala/tree/5709b66e
Diff: http://git-wip-us.apache.org/repos/asf/incubator-impala/diff/5709b66e
Branch: refs/heads/master
Commit: 5709b66e91d057478db8f94d0ad249b1afdc9bb6
Parents: 6441ca6
Author: John Russell <jr...@cloudera.com>
Authored: Tue Feb 14 16:38:57 2017 -0800
Committer: Impala Public Jenkins <im...@gerrit.cloudera.org>
Committed: Mon Mar 13 17:51:43 2017 +0000
----------------------------------------------------------------------
docs/topics/impala_upgrading.xml | 298 +++-------------------------------
1 file changed, 22 insertions(+), 276 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/5709b66e/docs/topics/impala_upgrading.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_upgrading.xml b/docs/topics/impala_upgrading.xml
index 6098d77..2d29925 100644
--- a/docs/topics/impala_upgrading.xml
+++ b/docs/topics/impala_upgrading.xml
@@ -32,243 +32,24 @@ under the License.
<conbody>
<p>
- Upgrading Impala involves stopping Impala services, using your operating system's package management
- tool to upgrade Impala to the latest version, and then restarting Impala services.
+ Upgrading Impala involves building or acquiring new Impala-related binaries,
+ and then restarting Impala services.
</p>
- <note>
- <ul>
- <li>
- Each version of CDH 5 has an associated version of Impala, When you upgrade from CDH 4 to CDH 5, you get
- whichever version of Impala comes with the associated level of CDH. Depending on the version of Impala
- you were running on CDH 4, this could install a lower level of Impala on CDH 5. For example, if you
- upgrade to CDH 5.0 from CDH 4 plus Impala 1.4, the CDH 5.0 installation comes with Impala 1.3. Always
- check the associated level of Impala before upgrading to a specific version of CDH 5. Where practical,
- upgrade from CDH 4 to the latest CDH 5, which also has the latest Impala.
- </li>
-
- <li rev="ver" audience="hidden">
- When you upgrade Impala, also upgrade Cloudera Manager if necessary:
- <ul>
- <li>
- Users running Impala on CDH 5 must upgrade to Cloudera Manager 5.0.0 or higher.
- </li>
-
- <li>
- Users running Impala on CDH 4 must upgrade to Cloudera Manager 4.8 or higher. Cloudera Manager 4.8
- includes management support for the Impala catalog service, and is the minimum Cloudera Manager
- version you can use.
- </li>
-
- <li>
- Cloudera Manager is continually updated with configuration settings for features introduced in the
- latest Impala releases.
- </li>
- </ul>
- </li>
-
- <li>
- If you are upgrading from CDH 5 beta to CDH 5.0 production, make sure you are using the appropriate CDH 5
- repositories shown on the
-<!-- Original URL: http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/latest/CDH-Version-and-Packaging-Information/CDH-Version-and-Packaging-Information.html -->
- <xref href="http://www.cloudera.com/documentation/enterprise/latest/topics/rg_vd.html" scope="external" format="html">CDH
- version and packaging</xref> page, then follow the procedures throughout the rest of this section.
- </li>
-
- <li>
- Every time you upgrade to a new major or minor Impala release, see
- <xref href="impala_incompatible_changes.xml#incompatible_changes"/> in the <cite>Release Notes</cite> for
- any changes needed in your source code, startup scripts, and so on.
- </li>
-
- <li>
- Also check <xref href="impala_known_issues.xml#known_issues"/> in the <cite>Release Notes</cite> for any
- issues or limitations that require workarounds.
- </li>
-
- </ul>
- </note>
-
- <p outputclass="toc inpage"/>
- </conbody>
-
- <concept id="upgrade_cm_parcels" audience="hidden">
-
- <title>Upgrading Impala through Cloudera Manager - Parcels</title>
- <prolog>
- <metadata>
- <data name="Category" value="Cloudera Manager"/>
- <data name="Category" value="Parcels"/>
- </metadata>
- </prolog>
-
- <conbody>
-
- <p>
- Parcels are an alternative binary distribution format available in Cloudera Manager 4.5 and higher.
- </p>
-
- <note type="important">
- In CDH 5, there is not a separate Impala parcel; Impala is part of the main CDH 5 parcel. Each level of CDH
- 5 has a corresponding version of Impala, and you upgrade Impala by upgrading CDH. See the
- <xref href="http://www.cloudera.com/documentation/enterprise/latest/topics/cm_mc_upgrading_cdh.html" scope="external" format="html">CDH
- 5 upgrade instructions</xref> and choose the instructions for parcels. The remainder of this section only covers parcel upgrades for
- Impala under CDH 4.
- </note>
-
- <p>
- To upgrade Impala for CDH 4 in a Cloudera Managed environment, using parcels:
- </p>
-
- <ol>
- <li>
- <p>
- If you originally installed using packages and now are switching to parcels, remove all the
- Impala-related packages first. You can check which packages are installed using one of the following
- commands, depending on your operating system:
- </p>
-<codeblock>rpm -qa # RHEL, Oracle Linux, CentOS, Debian
-dpkg --get-selections # Debian</codeblock>
- and then remove the packages using one of the following commands:
-<codeblock>sudo yum remove <varname>pkg_names</varname> # RHEL, Oracle Linux, CentOS
-sudo zypper remove <varname>pkg_names</varname> # SLES
-sudo apt-get purge <varname>pkg_names</varname> # Ubuntu, Debian</codeblock>
- </li>
-
- <li>
- <p>
- Connect to the Cloudera Manager Admin Console.
- </p>
- </li>
-
- <li>
- <p>
- Go to the <menucascade><uicontrol>Hosts</uicontrol><uicontrol>Parcels</uicontrol></menucascade> tab.
- You should see a parcel with a newer version of Impala that you can upgrade to.
- </p>
- </li>
-
- <li>
- <p>
- Click <uicontrol>Download</uicontrol>, then <uicontrol>Distribute</uicontrol>. (The button changes as
- each step completes.)
- </p>
- </li>
-
- <li>
- <p>
- Click <uicontrol>Activate</uicontrol>.
- </p>
- </li>
-
- <li>
- <p>
- When prompted, click <uicontrol>Restart</uicontrol> to restart the Impala service.
- </p>
- </li>
- </ol>
</conbody>
- </concept>
- <concept id="upgrade_cm_pkgs" audience="hidden">
+ <concept id="upgrade_manual">
- <title>Upgrading Impala through Cloudera Manager - Packages</title>
- <prolog>
- <metadata>
- <data name="Category" value="Packages"/>
- <data name="Category" value="Cloudera Manager"/>
- </metadata>
- </prolog>
+ <title>Upgrading Impala</title>
<conbody>
- <p>
- To upgrade Impala in a Cloudera Managed environment, using packages:
- </p>
-
- <ol>
- <li>
- Connect to the Cloudera Manager Admin Console.
- </li>
-
- <li>
- In the <b>Services</b> tab, click the <b>Impala</b> service.
- </li>
-
- <li>
- Click <b>Actions</b> and click <b>Stop</b>.
- </li>
-
- <li>
- Use <b>one</b> of the following sets of commands to update Impala on each Impala node in your cluster:
- <p>
- <b>For RHEL, Oracle Linux, or CentOS systems:</b>
- </p>
-<codeblock rev="1.2">$ sudo yum update impala
-$ sudo yum update hadoop-lzo-cdh4 # Optional; if this package is already installed
-</codeblock>
- <p>
- <b>For SUSE systems:</b>
- </p>
-<codeblock rev="1.2">$ sudo zypper update impala
-$ sudo zypper update hadoop-lzo-cdh4 # Optional; if this package is already installed
-</codeblock>
- <p>
- <b>For Debian or Ubuntu systems:</b>
- </p>
-<codeblock rev="1.2">$ sudo apt-get install impala
-$ sudo apt-get install hadoop-lzo-cdh4 # Optional; if this package is already installed
-</codeblock>
- </li>
-
+ <ul>
<li>
- Use <b>one</b> of the following sets of commands to update Impala shell on each node on which it is
- installed:
<p>
- <b>For RHEL, Oracle Linux, or CentOS systems:</b>
+ Shut down all Impala-related daemons on
+ all relevant hosts in the cluster:
</p>
-<codeblock>$ sudo yum update impala-shell</codeblock>
- <p>
- <b>For SUSE systems:</b>
- </p>
-<codeblock>$ sudo zypper update impala-shell</codeblock>
- <p>
- <b>For Debian or Ubuntu systems:</b>
- </p>
-<codeblock>$ sudo apt-get install impala-shell</codeblock>
- </li>
-
- <li>
- Connect to the Cloudera Manager Admin Console.
- </li>
-
- <li>
- In the <b>Services</b> tab, click the Impala service.
- </li>
-
- <li>
- Click <b>Actions</b> and click <b>Start</b>.
- </li>
- </ol>
- </conbody>
- </concept>
-
- <concept id="upgrade_noncm" rev="upstream">
-
- <title>Upgrading Impala</title>
- <prolog>
- <metadata>
- <!-- Fill in relevant metatag(s) when we decide how to mark non-CM topics. -->
- </metadata>
- </prolog>
-
- <conbody>
-
- <p> To upgrade Impala, run these Linux commands on the appropriate hosts in your cluster: </p>
-
- <ol>
- <li>
- Stop Impala services.
<ol>
<li>
Stop <codeph>impalad</codeph> on each Impala node in your cluster:
@@ -286,65 +67,30 @@ $ sudo apt-get install hadoop-lzo-cdh4 # Optional; if this package is already in
</li>
</ol>
</li>
-
<li>
- Check if there are new recommended or required configuration settings to put into place in the
- configuration files, typically under <filepath>/etc/impala/conf</filepath>. See
- <xref href="impala_config_performance.xml#config_performance"/> for settings related to performance and
- scalability.
- </li>
-
- <li>
- Use <b>one</b> of the following sets of commands to update Impala on each Impala node in your cluster:
- <p>
- <b>For RHEL, Oracle Linux, or CentOS systems:</b>
- </p>
-<codeblock>$ sudo yum update impala-server
-$ sudo yum update hadoop-lzo-cdh4 # Optional; if this package is already installed
-$ sudo yum update impala-catalog # New in Impala 1.2; do yum install when upgrading from 1.1.
-</codeblock>
<p>
- <b>For SUSE systems:</b>
+ Follow the build procedure in the
+ <filepath>README.md</filepath> file
+ to produce new Impala binaries.
</p>
-<codeblock>$ sudo zypper update impala-server
-$ sudo zypper update hadoop-lzo-cdh4 # Optional; if this package is already installed
-$ sudo zypper update impala-catalog # New in Impala 1.2; do zypper install when upgrading from 1.1.
-</codeblock>
- <p>
- <b>For Debian or Ubuntu systems:</b>
- </p>
-<codeblock>$ sudo apt-get install impala-server
-$ sudo apt-get install hadoop-lzo-cdh4 # Optional; if this package is already installed
-$ sudo apt-get install impala-catalog # New in Impala 1.2.
-</codeblock>
</li>
-
<li>
- Use <b>one</b> of the following sets of commands to update Impala shell on each node on which it is
- installed:
<p>
- <b>For RHEL, Oracle Linux, or CentOS systems:</b>
+ Replace the binaries for all Impala-related
+ daemons on all relevant hosts in the cluster.
</p>
-<codeblock>$ sudo yum update impala-shell</codeblock>
- <p>
- <b>For SUSE systems:</b>
- </p>
-<codeblock>$ sudo zypper update impala-shell</codeblock>
- <p>
- <b>For Debian or Ubuntu systems:</b>
- </p>
-<codeblock>$ sudo apt-get install impala-shell</codeblock>
</li>
-
- <li rev="alternatives">
- Depending on which release of Impala you are upgrading from, you might find that the symbolic links
- <filepath>/etc/impala/conf</filepath> and <filepath>/usr/lib/impala/sbin</filepath> are missing. If so,
- see <xref href="impala_known_issues.xml#known_issues"/> for the procedure to work around this
- problem.
+ <li>
+ Check if there are new recommended or required configuration settings to put into place in the
+ configuration files, typically under <filepath>/etc/impala/conf</filepath>. See
+ <xref href="impala_config_performance.xml#config_performance"/> for settings related to performance and
+ scalability.
</li>
-
<li>
- Restart Impala services:
+ <p>
+ Restart all Impala-related daemons on
+ all relevant hosts in the cluster:
+ </p>
<ol>
<li>
Restart the Impala state store service on the desired nodes in your cluster. Expect to see a process
@@ -379,7 +125,7 @@ $ ps ax | grep [i]mpalad
</li>
</ol>
</li>
- </ol>
+ </ul>
<note>
<p>