This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new 7d2b63ee Automatic Site Publish by Buildbot
7d2b63ee is described below
commit 7d2b63ee96b4494e9d8f3b19e8b4b9d0f25d5bc6
Author: buildbot <[email protected]>
AuthorDate: Wed Nov 16 05:21:45 2022 +0000
Automatic Site Publish by Buildbot
---
output/docs/2.x/administration/upgrading.html | 158 ++++++++++++------------
output/docs/2.x/getting-started/quickstart.html | 6 +-
output/docs/2.x/troubleshooting/tools.html | 2 +-
output/feed.xml | 4 +-
output/search_data.json | 4 +-
5 files changed, 90 insertions(+), 84 deletions(-)
diff --git a/output/docs/2.x/administration/upgrading.html
b/output/docs/2.x/administration/upgrading.html
index 5b6b96c0..18d4f1f8 100644
--- a/output/docs/2.x/administration/upgrading.html
+++ b/output/docs/2.x/administration/upgrading.html
@@ -430,103 +430,95 @@
</div>
- <h2 id="upgrading-from-110x-or-20x-to-21">Upgrading from 1.10.x or 2.0.x
to 2.1</h2>
+ <h2 id="upgrading-from-110-or-20-to-21">Upgrading from 1.10 or 2.0 to
2.1</h2>
-<p>The recommended way to upgrade from a prior 1.10.x or 2.0.x release is to
stop Accumulo, upgrade
-to 2.1 and then start 2.1. To upgrade from a release prior to 1.10, follow the
-<a href="#upgrading-from-18910-to-20">below steps</a> to upgrade to at least
1.10 and then perform the upgrade to 2.1. A
-direct upgrade from releases prior to 1.10 has not been tested.</p>
+<p>Please read these directions in their entirety before beginning. Please <a
href="/contact-us">contact</a> us with any
+questions you have about this process.</p>
-<p>Important: before starting any upgrade process you need to make sure there
are no outstanding FATE transactions. This
-includes transactions that have completed with <code class="language-plaintext
highlighter-rouge">SUCCESS</code> or <code class="language-plaintext
highlighter-rouge">FAILED</code> but have not been removed by the automatic
clean-up
-process. This is required because the internal serialization of FATE
transactions is not guaranteed to be compatible
-between versions, so <em>ANY</em> FATE transaction that is present will fail
the upgrade. Procedures to manage FATE
-transactions, including commands to fail and delete transactions, are included
in the Accumulo documentation
-<a href="/docs/2.x/administration/fate#administration">FATE -
Administration</a></p>
+<p><strong>IMPORTANT!</strong> Before running any Accumulo 2.1 upgrade
utilities or services, you will need to
+upgrade to Java 11, Hadoop 3, and at least ZooKeeper 3.5 (at least 3.8 was
current at the time of
+this writing and is recommended).</p>
-<p>Two significant changes from 1.10.x/2.0 to 2.1 that are important to
note:</p>
+<p>The basic upgrade sequence is:</p>
+
+<ul>
+ <li>upgrade to at least Accumulo 1.10 first (if necessary)</li>
+ <li>stop Accumulo 1.10 or 2.0</li>
+ <li>prepare your installation of Accumulo 2.1 through whatever means you
obtain the binaries and
+configure it in your environment</li>
+ <li>(optional - but recommended) create a ZooKeeper snapshot</li>
+ <li>(required if not using the provided scripts to start 2.1) run the <code
class="language-plaintext highlighter-rouge">RenameMasterDirInZK</code>
utility</li>
+ <li>(optional) run the pre-upgrade utility to convert the configuration in
ZooKeeper</li>
+ <li>start Accumulo 2.1 for the first time to complete the upgrade</li>
+</ul>
+
+<p><strong>IMPORTANT!</strong> before starting any upgrade process you need to
make sure there are no outstanding
+FATE transactions. This includes transactions that have completed with <code
class="language-plaintext highlighter-rouge">SUCCESS</code> or <code
class="language-plaintext highlighter-rouge">FAILED</code> but
+have not been removed by the automatic clean-up process. This is required
because the internal
+serialization of FATE transactions is not guaranteed to be compatible between
versions, so <em>ANY</em>
+FATE transaction that is present will fail the upgrade. Procedures to manage
FATE transactions,
+including commands to fail and delete transactions, are included in the <a
href="/docs/2.x/administration/fate#administration">FATE Administration
+documentation</a>.</p>
+
+<p>Two significant changes occurred in 2.1 that are particularly important to
note for upgrades:</p>
<ol>
<li>properties and services that referenced <code class="language-plaintext
highlighter-rouge">master</code> are renamed <code class="language-plaintext
highlighter-rouge">manager</code> and</li>
- <li>the property storage in ZooKeeper has changed from a ZooKeeper node per
property to a single node for all
-properties with a single ZooKeeper property node for each table, namespace.
and the system config properties.</li>
+ <li>the internal property storage format in ZooKeeper has changed - instead
of each table, namespace,
+and the system configuration using separate ZooKeeper nodes for each of their
properties, they
+each now use only a single ZooKeeper node for all of their respective
properties.</li>
</ol>
-<p>Before upgrading to 2.1, it is suggested that you create a snapshot of the
current ZooKeeper contents to be a backup
-in case issues occur and you need to rollback. There are no provisions to
roll back to a previous Accumulo version
-once an upgrade process has been completed other than restoring from a
snapshot of ZooKeeper.</p>
+<p>Details on renaming the properties and the ZooKeeper property conversion
are provided in the
+following sections. Additional information on configuring 2.1 is <a
href="/docs/2.x/administration/in-depth-install">available here</a>.</p>
-<p>Details on renaming the properties and the ZooKeeper property conversion
provided in sections that follow.</p>
-
-<h3 id="rename-master-properties-config-files-and-script-references">Rename
master Properties, Config Files, and Script References</h3>
-
-<p>Although not required until at least release 3.0, it is strongly
recommended as a part of the
-upgrade to rename any properties in <code class="language-plaintext
highlighter-rouge">accumulo.properties</code> (or properties specified on the
command
-line) starting with <code class="language-plaintext
highlighter-rouge">master.</code>. <code class="language-plaintext
highlighter-rouge">master</code> should be replaced with <code
class="language-plaintext highlighter-rouge">manager</code>.</p>
+<h3 id="create-zookeeper-snapshot-optional---but-recommended">Create ZooKeeper
snapshot (optional - but recommended)</h3>
-<p>Any reference to <code class="language-plaintext
highlighter-rouge">master</code> in other scripts (e.g., invoking <code
class="language-plaintext highlighter-rouge">accumulo-service master</code>
from an init
-script) should be renamed to <code class="language-plaintext
highlighter-rouge">manager</code> (<code class="language-plaintext
highlighter-rouge">accumulo-service manager</code> for the previous
example).</p>
+<p>Before upgrading to 2.1, it is suggested that you create a snapshot of the
current ZooKeeper
+contents to be a backup in case issues occur and you need to rollback. There
are no provisions to
+roll back to a previous Accumulo version once an upgrade process has been
completed other than
+restoring from a snapshot of ZooKeeper.</p>
-<p>If the manager is not started using the provided <code
class="language-plaintext highlighter-rouge">accumulo-cluster</code> or <code
class="language-plaintext highlighter-rouge">accumulo-service</code> scripts,
-then a one-time upgrade step will need to be performed. Run the <code
class="language-plaintext highlighter-rouge">RenameMasterDirInZK</code> utility
-after installing 2.1 but before starting it.</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>${ACCUMULO_HOME}/bin/accumulo
org.apache.accumulo.manager.upgrade.RenameMasterDirInZK
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>$ACCUMULO_HOME/bin/accumulo dump-zoo --xml --root
/accumulo | tee PATH_TO_SNAPSHOT
</code></pre></div></div>
-<h3 id="create-new-cluster-configuration-file">Create new cluster
configuration file</h3>
-
-<p>The <code class="language-plaintext
highlighter-rouge">accumulo-cluster</code> script now uses a single file that
defines the location of the managers,
-tservers, etc. You can create this file using the command <code
class="language-plaintext highlighter-rouge">accumulo-cluster
create-config</code>. You
-will then need to transfer the contents of the current individual files to
this new consolidated file.</p>
-
-<h3 id="encrypted-instances">Encrypted Instances</h3>
-
-<p><strong>Warning</strong>: Upgrading a previously encrypted instance is not
supported as the implementation
-and properties have changed.</p>
-
-<h2 id="upgrading-from-1911020-to-21">Upgrading from 1.9/1.10/2.0 to 2.1</h2>
+<p>If you need to restore from the ZooKeeper snapshot see <a
href="/docs/2.x/troubleshooting/tools#restorezookeeper">these
instructions</a>.</p>
-<p>Note: the process for upgrading to 2.1 assumes that you have already
upgraded to 1.10 or 2.0. Upgrading from a
-version prior to 1.10 may work, but is unsupported and untested. If you are
upgrading from 1.10 make sure
-that you have adjusted for the <code class="language-plaintext
highlighter-rouge">master</code> to <code class="language-plaintext
highlighter-rouge">manager</code> and other configuration changes as described
in the
-Upgrading from 1.8/9/10 to 2.0 <a href="#upgrading-from-18910-to-20">below
steps</a>.</p>
-
-<p>Additional information on configuring 2.1 is available at
(/docs/2.x//in-depth-installation)</p>
-
-<p>The particular order for your installation will differ depending on how you
choose to install Accumulo.<br />
-The key part being that the upgrade utilities need to be run with 2.1 code on
a stopped 1.10 / 2.0 instance.</p>
-
-<p>You can elect to stop your current instance, install and configure the 2.1
binaries, optionally run the upgrade
-utilities and then start 2.1, or you could install and configure the 2.1
binaries while your instance remains
-running and then when ready, stop your instance, optionally run the upgrade
utilities and then start 2.1.</p>
+<h3 id="rename-master-properties-config-files-and-script-references">Rename
master Properties, Config Files, and Script References</h3>
-<p>The basic upgrade sequence is to:</p>
+<p>It is strongly recommended as a part of the upgrade to rename any
properties in
+<code class="language-plaintext highlighter-rouge">accumulo.properties</code>
(or properties specified on the command line) starting with <code
class="language-plaintext highlighter-rouge">master.</code> to use
+the equivalent property starting with <code class="language-plaintext
highlighter-rouge">manager.</code> instead, as the old properties will not be
+available in subsequent major releases. This version may log or display
warnings if older properties
+are observed.</p>
-<ul>
- <li>stop Accumulo (1.10/2.0)</li>
- <li>update your environment to point to 2.1 executable path.</li>
- <li>(optional - but recommended) create a ZooKeeper snapshot</li>
- <li>(optional) run the configuration upgrade utility</li>
- <li>start Accumulo 2.1</li>
-</ul>
+<p>Any reference to <code class="language-plaintext
highlighter-rouge">master</code> in other scripts (e.g., invoking <code
class="language-plaintext highlighter-rouge">accumulo-service master</code>
from an init
+script) should be renamed to <code class="language-plaintext
highlighter-rouge">manager</code> (for example, <code class="language-plaintext
highlighter-rouge">accumulo-service manager</code>).</p>
-<h3 id="create-zookeeper-snapshot-optional---but-recommended">Create ZooKeeper
snapshot (optional - but recommended)</h3>
+<p>If the manager is not started using the provided <code
class="language-plaintext highlighter-rouge">accumulo-cluster</code> or <code
class="language-plaintext highlighter-rouge">accumulo-service</code> scripts,
+then a one-time upgrade step will need to be performed. Run the <code
class="language-plaintext highlighter-rouge">RenameMasterDirInZK</code> utility
after
+installing 2.1 but before starting it.</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>$ACCUMULO_HOME/bin/accumulo dump-zoo --xml --root
/accumulo | tee PATH_TO_SNAPSHOT
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>${ACCUMULO_HOME}/bin/accumulo
org.apache.accumulo.manager.upgrade.RenameMasterDirInZK
</code></pre></div></div>
-<p>If you need to restore from the ZooKeeper snapshot see
(/docs/2.x/troubleshooting/tools )</p>
+<h3 id="pre-upgrade-the-property-storage-in-zookeeper-optional">Pre-Upgrade
the property storage in ZooKeeper (optional)</h3>
-<h3 id="upgrade-the-property-storage-in-zookeeper-optional">Upgrade the
property storage in ZooKeeper (optional)</h3>
+<p>As mentioned above, the property storage in ZooKeeper has changed from many
nodes per table,
+namespace, and the system configuration, to just a single node for each of
those. Upgrading to use
+the new format does happen automatically when Accumulo 2.1 servers start up.
However, you can
+optionally choose to convert them using a pre-upgrade step with the following
command line utility.</p>
-<p>The property conversion can be done using a command line utility or it will
occur automatically when the manager is
-started for the first time. Using the command line utility is optional, but
may provide more flexibility in
-handling issues if they were to occur. With ZooKeeper running, the command to
convert the properties is:</p>
+<p>The property conversion can be done using a command line utility or it will
occur automatically when
+the manager is started for the first time. Using the command line utility is
optional, but may
+provide more flexibility in handling issues if they were to occur. With
ZooKeeper running, the
+command to convert the properties is:</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>$ACCUMULO_HOME/bin/accumulo config-upgrade
</code></pre></div></div>
-<p>The utility will print progress and a count of the number of properties
converted (as delete count) and an error count</p>
+<p>The utility will print messages about its progress as it converts them.</p>
+
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>2022-11-03T14:35:44,596 [conf.SiteConfiguration] INFO :
Found Accumulo configuration on classpath at
/opt/fluo-uno/install/accumulo-3.0.0-SNAPSHOT/conf/accumulo.properties
2022-11-03T14:35:45,511 [util.ConfigPropertyUpgrader] INFO : Upgrade system
config properties for a1518a8b-f007-41ee-af2c-5cc760abe7fd
2022-11-03T14:35:45,675 [util.ConfigTransformer] INFO : property transform for
SystemPropKey{InstanceId=a1518a8b-f007-41ee-af2c-5cc760abe7fd'} took 29ms ms,
delete count: 1, error count: 0
@@ -536,15 +528,29 @@ handling issues if they were to occur. With ZooKeeper
running, the command to c
2022-11-03T14:35:45,813 [util.ConfigTransformer] INFO : property transform for
TablePropKey{TableId=!0'} took 72ms ms, delete count: 26, error count: 0
...
</code></pre></div></div>
-<p>If the upgrade utility is not used, similar messages will be printed to the
manager log on the first 2.1 version
-manager start up.</p>
-<p>When the property conversion is complete, you can verify the configuration
using the zoo-info-viewer utility
-(new in 2.1)</p>
+<p>If the upgrade utility is not used, similar messages will print to the
server logs when 2.1 starts.</p>
+
+<p>When the property conversion is complete, you can verify the configuration
using the
+<a
href="/docs/2.x//troubleshooting/tools#zoo-info-viewer-new-in-21">zoo-info-viewer</a>
utility (new in 2.1)</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>$ACCUMULO_HOME/bin/accumulo zoo-info-viewer
--print-props
</code></pre></div></div>
+<h3 id="create-new-cluster-configuration-file">Create new cluster
configuration file</h3>
+
+<p>The <code class="language-plaintext
highlighter-rouge">accumulo-cluster</code> script now uses a single file that
defines the location of the managers,
+tservers, etc. You can create this file using the command <code
class="language-plaintext highlighter-rouge">accumulo-cluster
create-config</code>. You will
+then need to transfer the contents of the current individual files to this new
consolidated file.</p>
+
+<h3 id="encrypted-instances">Encrypted Instances</h3>
+
+<p><strong>Warning</strong>: Upgrading a previously encrypted instance with
the experimental encryption properties
+is not supported as the implementation and properties have changed. You may be
able to disable
+encryption and compact your files without encryption, in order to upgrade.
Encryption remains an
+experimental feature, and may change between versions. It should be used with
care. If you need
+help, consider reaching out to our mailing list.</p>
+
<h2 id="upgrading-from-18910-to-20">Upgrading from 1.8/9/10 to 2.0</h2>
<p>Follow the steps below to upgrade your Accumulo instance and client to
2.0.</p>
@@ -589,7 +595,7 @@ in the new file are different so take care when
customizing.</li>
<ul>
<li>This file was used in Accumulo 1.x but has changed significantly for
2.0</li>
<li>Environment variables (such as <code class="language-plaintext
highlighter-rouge">$cmd</code>, <code class="language-plaintext
highlighter-rouge">$bin</code>, <code class="language-plaintext
highlighter-rouge">$conf</code>) are set before <code class="language-plaintext
highlighter-rouge">accumulo-env.sh</code> is loaded and can be used to
customize environment.</li>
- <li>The <code class="language-plaintext
highlighter-rouge">JAVA_OPTS</code> variable is constructed in <code
class="language-plaintext highlighter-rouge">accumulo-env.sh</code> to pass
command-line arguments to the <code class="language-plaintext
highlighter-rouge">java</code> command that the starts Accumulo processes
+ <li>The <code class="language-plaintext
highlighter-rouge">JAVA_OPTS</code> variable is constructed in <code
class="language-plaintext highlighter-rouge">accumulo-env.sh</code> to pass
command line arguments to the <code class="language-plaintext
highlighter-rouge">java</code> command that the starts Accumulo processes
(i.e. <code class="language-plaintext highlighter-rouge">java $JAVA_OPTS
main.class.for.$cmd</code>).</li>
<li>The <code class="language-plaintext
highlighter-rouge">CLASSPATH</code> variable sets the Java classpath used when
running Accumulo processes. It can be modified to upgrade dependencies or use
vendor-specific
distributions of Hadoop.</li>
diff --git a/output/docs/2.x/getting-started/quickstart.html
b/output/docs/2.x/getting-started/quickstart.html
index a7133f97..8f931b21 100644
--- a/output/docs/2.x/getting-started/quickstart.html
+++ b/output/docs/2.x/getting-started/quickstart.html
@@ -594,11 +594,11 @@ and the shell will prompt you for the password of <code
class="language-plaintex
<h2 id="initialization">Initialization</h2>
-<p>Accumulo needs to initialize the locations where it stores data in
Zookeeper and
-HDFS.</p>
+<p>Accumulo needs to initialize the locations where it stores data in
Zookeeper and HDFS.</p>
<p>Note: Initialization only needs to be performed once for an instance - if
you are performing an
-upgrade you should not run the initialization command a second time unless you
really want a new instance</p>
+upgrade you should not run the initialization command a second time unless you
really want a new
+instance.</p>
<p>The following command will perform the initialization.</p>
diff --git a/output/docs/2.x/troubleshooting/tools.html
b/output/docs/2.x/troubleshooting/tools.html
index 44a017f9..5cecd05c 100644
--- a/output/docs/2.x/troubleshooting/tools.html
+++ b/output/docs/2.x/troubleshooting/tools.html
@@ -705,7 +705,7 @@ Checking table t3
Tablet 3<< is located at localhost:9997
</code></pre></div></div>
-<h1 id="zoo-info-viewer-new-in-21">zoo-info-viewer (new in 2.1)</h1>
+<h2 id="zoo-info-viewer-new-in-21">zoo-info-viewer (new in 2.1)</h2>
<p>View Accumulo information stored in ZooKeeper in a human-readable format.
The utility can be run without an Accumulo
instance. If an instance id or name is not provided on the command line, the
instance will be read from
diff --git a/output/feed.xml b/output/feed.xml
index 4920eb44..f2dee3b9 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -6,8 +6,8 @@
</description>
<link>https://accumulo.apache.org/</link>
<atom:link href="https://accumulo.apache.org/feed.xml"; rel="self"
type="application/rss+xml"/>
- <pubDate>Wed, 16 Nov 2022 05:20:21 +0000</pubDate>
- <lastBuildDate>Wed, 16 Nov 2022 05:20:21 +0000</lastBuildDate>
+ <pubDate>Wed, 16 Nov 2022 05:21:38 +0000</pubDate>
+ <lastBuildDate>Wed, 16 Nov 2022 05:21:38 +0000</lastBuildDate>
<generator>Jekyll v4.3.1</generator>
diff --git a/output/search_data.json b/output/search_data.json
index b3f00aca..5661c1de 100644
--- a/output/search_data.json
+++ b/output/search_data.json
@@ -65,7 +65,7 @@
"docs-2-x-administration-upgrading": {
"title": "Upgrading Accumulo",
- "content": "Upgrading from 1.10.x or 2.0.x to 2.1The recommended way to
upgrade from a prior 1.10.x or 2.0.x release is to stop Accumulo, upgradeto 2.1
and then start 2.1. To upgrade from a release prior to 1.10, follow thebelow
steps to upgrade to at least 1.10 and then perform the upgrade to 2.1. Adirect
upgrade from releases prior to 1.10 has not been tested.Important: before
starting any upgrade process you need to make sure there are no outstanding
FATE transactions. Thisinclu [...]
+ "content": "Upgrading from 1.10 or 2.0 to 2.1Please read these
directions in their entirety before beginning. Please contact us with
anyquestions you have about this process.IMPORTANT! Before running any Accumulo
2.1 upgrade utilities or services, you will need toupgrade to Java 11, Hadoop
3, and at least ZooKeeper 3.5 (at least 3.8 was current at the time ofthis
writing and is recommended).The basic upgrade sequence is: upgrade to at least
Accumulo 1.10 first (if necessary) stop [...]
"url": " /docs/2.x/administration/upgrading",
"categories": "administration"
},
@@ -184,7 +184,7 @@
"docs-2-x-getting-started-quickstart": {
"title": "Setup",
- "content": "User Manual (2.x)Starting with Accumulo 2.0, the user manual
now lives on the website as a seriesof web pages. Previously, it was one large
pdf document that was only generatedduring a release. The user manual can now
be updated very quickly and indexedfor searching across many webpages.The
manual can now be searched using the Search link at the top of thewebsite or
navigated by clicking the links to the left. If you are new toAccumulo, follow
the instructions below to [...]
+ "content": "User Manual (2.x)Starting with Accumulo 2.0, the user manual
now lives on the website as a seriesof web pages. Previously, it was one large
pdf document that was only generatedduring a release. The user manual can now
be updated very quickly and indexedfor searching across many webpages.The
manual can now be searched using the Search link at the top of thewebsite or
navigated by clicking the links to the left. If you are new toAccumulo, follow
the instructions below to [...]
"url": " /docs/2.x/getting-started/quickstart",
"categories": "getting-started"
},
