This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 3d921599d Automatic Site Publish by Buildbot
3d921599d is described below
commit 3d921599d332c73e1fa1230566a72102e02d8ae1
Author: buildbot <[email protected]>
AuthorDate: Tue Sep 29 19:00:14 2026 +0000
Automatic Site Publish by Buildbot
---
.../docs/4.x/administration/in-depth-install.html | 221 +++++++++------------
output/feed.xml | 4 +-
2 files changed, 93 insertions(+), 132 deletions(-)
diff --git a/output/docs/4.x/administration/in-depth-install.html
b/output/docs/4.x/administration/in-depth-install.html
index 381fef210..c7b7505f4 100644
--- a/output/docs/4.x/administration/in-depth-install.html
+++ b/output/docs/4.x/administration/in-depth-install.html
@@ -437,7 +437,7 @@ communicate with HDFS. To achieve good ingest and query
performance, sufficient
network bandwidth must be available between any two machines.</p>
<p>In addition to needing access to ports associated with HDFS and ZooKeeper,
Accumulo will
-use the following default ports. Please make sure that they are open, or change
+use the following default ports and port ranges. Please make sure that they
are open, or change
their value in <a
href="/docs/4.x/configuration/files#accumuloproperties">accumulo.properties</a>.</p>
<table>
@@ -455,12 +455,7 @@ their value in <a
href="/docs/4.x/configuration/files#accumuloproperties">accumu
<td>n/a</td>
</tr>
<tr>
- <td>9132</td>
- <td>Accumulo Compaction Coordinator</td>
- <td><a
href="/docs/4.x/configuration/server-properties#compaction_coordinator_port_client">compaction.coordinator.port.client</a></td>
- </tr>
- <tr>
- <td>9133</td>
+ <td>9600-9699</td>
<td>Accumulo Compactor</td>
<td><a
href="/docs/4.x/configuration/server-properties#compactor_port_client">compactor.port.client</a></td>
</tr>
@@ -470,12 +465,12 @@ their value in <a
href="/docs/4.x/configuration/files#accumuloproperties">accumu
<td><a
href="/docs/4.x/configuration/server-properties#monitor_port_client">monitor.port.client</a></td>
</tr>
<tr>
- <td>9996</td>
+ <td>9700-9799</td>
<td>Accumulo Scan Server</td>
<td><a
href="/docs/4.x/configuration/server-properties#sserver_port_client">sserver.port.client</a></td>
</tr>
<tr>
- <td>9997</td>
+ <td>9800-9899</td>
<td>Accumulo Tablet Server</td>
<td><a
href="/docs/4.x/configuration/server-properties#tserver_port_client">tserver.port.client</a></td>
</tr>
@@ -485,30 +480,15 @@ their value in <a
href="/docs/4.x/configuration/files#accumuloproperties">accumu
<td><a
href="/docs/4.x/configuration/server-properties#gc_port_client">gc.port.client</a></td>
</tr>
<tr>
- <td>9999</td>
+ <td>9999-10009</td>
<td>Accumulo Manager Server</td>
<td><a
href="/docs/4.x/configuration/server-properties#manager_port_client">manager.port.client</a></td>
</tr>
- <tr>
- <td>12234</td>
- <td>Accumulo Tracer</td>
- <td><a
href="/docs/4.x/configuration/server-properties#trace_port_client">trace.port.client</a></td>
- </tr>
<tr>
<td>42424</td>
<td>Accumulo Proxy Server</td>
<td>n/a</td>
</tr>
- <tr>
- <td>10001</td>
- <td>Accumulo Manager Replication service</td>
- <td><a
href="/docs/4.x/configuration/server-properties#manager_replication_coordinator_port">manager.replication.coordinator.port</a></td>
- </tr>
- <tr>
- <td>10002</td>
- <td>Accumulo TabletServer Replication service</td>
- <td><a
href="/docs/4.x/configuration/server-properties#replication_receipt_service_port">replication.receipt.service.port</a></td>
- </tr>
</tbody>
</table>
@@ -516,10 +496,10 @@ their value in <a
href="/docs/4.x/configuration/files#accumuloproperties">accumu
ephemeral port is likely to be unique and not already bound. Thus, configuring
ports to
use <code class="language-plaintext highlighter-rouge">0</code> instead of an
explicit value, should, in most cases, work around any issues of
running multiple distinct Accumulo instances (or any other process which tries
to use the
-same default ports) on the same hardware. Finally, the <code
class="language-plaintext highlighter-rouge">*.port.client</code> properties
will work
-with the port range syntax (M-N) allowing the user to specify a range of ports
for the
-service to attempt to bind. The ports in the range will be tried in a 1-up
manner starting
-at the low end of the range to, and including, the high end of the range.</p>
+same default ports) on the same hardware. The port range syntax (M-N) allows
the user to
+specify a range of ports for the service to attempt to bind. The ports in the
range will
+be tried in a 1-up manner starting at the low end of the range to, and
including, the high
+end of the range.</p>
<h2 id="download-tarball">Download Tarball</h2>
@@ -564,7 +544,7 @@ exist in <code class="language-plaintext
highlighter-rouge">conf/</code> and be
cluster, the <code class="language-plaintext highlighter-rouge">conf/</code>
directory must also contain a <code class="language-plaintext
highlighter-rouge">cluster.yaml</code> file. You can either create these files
manually or run <code class="language-plaintext
highlighter-rouge">accumulo-cluster create-config</code>.</p>
-<p>Logging is configured in <a
href="/docs/4.x/configuration/files#accumulo-envsh">accumulo-env.sh</a> to use
three log4j configuration files in <code class="language-plaintext
highlighter-rouge">conf/</code>. The
+<p>Logging is configured in <a
href="/docs/4.x/configuration/files#accumulo-envsh">accumulo-env.sh</a> to use
two log4j configuration files in <code class="language-plaintext
highlighter-rouge">conf/</code>. The
file used depends on the Accumulo command or service being run. Logging for
most Accumulo services
(i.e. Manager, TabletServer, Garbage Collector) is configured by <a
href="/docs/4.x/configuration/files#log4j2-serviceproperties">log4j2-service.properties</a>.
All Accumulo commands (i.e <code class="language-plaintext
highlighter-rouge">init</code>,
<code class="language-plaintext highlighter-rouge">shell</code>, etc) are
configured by <a
href="/docs/4.x/configuration/files#log4j2properties">log4j2.properties</a>.</p>
@@ -647,15 +627,15 @@ native map.</p>
this value, it is also important to adjust the values below:</p>
<ul>
- <li><a
href="/docs/4.x/configuration/server-properties#table_compaction_minor_logs_threshold">table.compaction.minor.logs.threshold</a>
- maximum number of write-ahead log files that a tablet
+ <li><a
href="/docs/4.x/configuration/server-properties#tserver_wal_max_referenced">tserver.wal.max.referenced</a>
- maximum number of write-ahead log files that a tablet
can reference before they will be automatically minor compacted</li>
- <li><a
href="/docs/4.x/configuration/server-properties#tserver_walog_max_size">tserver.walog.max.size</a>
- maximum size of a write-ahead log.</li>
+ <li><a
href="/docs/4.x/configuration/server-properties#tserver_wal_max_size">tserver.wal.max.size</a>
- maximum size of a write-ahead log.</li>
</ul>
<p>The maximum size of the native maps for a server should be less than the
product of the write-ahead
log maximum size and minor compaction threshold for log files:</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>$table.compaction.minor.logs.threshold *
$tserver.walog.max.size >= $tserver.memory.maps.max
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>$tserver.wal.max.referenced * $tserver.wal.max.size
>= $tserver.memory.maps.max
</code></pre></div></div>
<p>This formula ensures that minor compactions won’t be automatically
triggered before the native
@@ -664,25 +644,55 @@ maps can be completely saturated.</p>
<p>Subsequently, when increasing the size of the write-ahead logs, it can also
be important
to increase the HDFS block size that Accumulo uses when creating the files for
the write-ahead log.
This is controlled via <a
href="/docs/4.x/configuration/server-properties#tserver_wal_blocksize">tserver.wal.blocksize</a>.
A basic recommendation is that when
-<a
href="/docs/4.x/configuration/server-properties#tserver_walog_max_size">tserver.walog.max.size</a>
is larger than 2GB in size, set <a
href="/docs/4.x/configuration/server-properties#tserver_wal_blocksize">tserver.wal.blocksize</a>
to 2GB.
+<a
href="/docs/4.x/configuration/server-properties#tserver_wal_max_size">tserver.wal.max.size</a>
is larger than 2GB in size, set <a
href="/docs/4.x/configuration/server-properties#tserver_wal_blocksize">tserver.wal.blocksize</a>
to 2GB.
Increasing the block size to a value larger than 2GB can result in decreased
write
performance to the write-ahead log file which will slow ingest.</p>
<h3 id="cluster-specification">Cluster Specification</h3>
-<p>If you are using <code class="language-plaintext
highlighter-rouge">accumulo-cluster</code> to start a cluster, configure the
following on the
-machine that will serve as the Accumulo manager:</p>
+<p>If you are using <code class="language-plaintext
highlighter-rouge">accumulo-cluster</code> to manage a cluster, then you need
to generate and
+modify the <code class="language-plaintext
highlighter-rouge">cluster.yaml</code> file. The <code
class="language-plaintext highlighter-rouge">cluster.yaml</code> file can be
created by running
+<code class="language-plaintext highlighter-rouge">accumulo-cluster
create-config</code> and will create the following file:</p>
+
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>manager:
+ servers_per_host: 1
+ hosts:
+ - localhost
+
+monitor:
+ - localhost
+
+gc:
+ - localhost
+
+tserver:
+ default:
+ servers_per_host: 1
+ hosts:
+ - localhost
+
+compactor:
+ default:
+ servers_per_host: 1
+ hosts:
+ - localhost
+
+sserver:
+ default:
+ servers_per_host: 1
+ hosts:
+ - localhost
+</code></pre></div></div>
-<ol>
- <li>Run <code class="language-plaintext highlighter-rouge">accumulo-cluster
create-config</code> to create the <code class="language-plaintext
highlighter-rouge">cluster.yaml</code> file.</li>
- <li>Write the IP address or domain name of the Accumulo Manager to the <a
href="/docs/4.x/configuration/files#manager">manager</a> section.</li>
- <li>Write the IP addresses or domain name of the machines that will be
TabletServers to the
-<a href="/docs/4.x/configuration/files#tserver">tserver</a> section.</li>
-</ol>
+<p>For each server type you will need to modify the list of hosts using either
+IP address or domain name. If using domain names rather than IP addresses,
+then DNS must be configured properly for all machines participating in the
cluster.</p>
-<p>Note that if using domain names rather than IP addresses, DNS must be
configured
-properly for all machines participating in the cluster. DNS can be a confusing
source
-of errors.</p>
+<p>In the example above the compactor, sserver, and tserver sections support
+the user specifying different resource groups. The example only contains the
+<code class="language-plaintext highlighter-rouge">default</code> resource
group. When adding resource groups to this file, be sure
+to also add them to the <code class="language-plaintext
highlighter-rouge">accumulo-env.sh</code> file and to create them using
+the command <code class="language-plaintext highlighter-rouge">accumulo inst
init --add-resource-groups <comma-separated group names></code>.</p>
<h3 id="configure-accumuloproperties">Configure accumulo.properties</h3>
@@ -719,15 +729,14 @@ instance, Accumulo identifies <code
class="language-plaintext highlighter-rouge"
<h3 id="deploy-configuration">Deploy Configuration</h3>
<p>Copy <a
href="/docs/4.x/configuration/files#accumulo-envsh">accumulo-env.sh</a> and <a
href="/docs/4.x/configuration/files#accumuloproperties">accumulo.properties</a>
from the <code class="language-plaintext highlighter-rouge">conf/</code>
directory on the manager to all
-Accumulo tablet servers. The “host” configuration files <code
class="language-plaintext highlighter-rouge">accumulo-cluster</code> only need
to be on
+hosts running Accumulo server processes. The <code class="language-plaintext
highlighter-rouge">cluster.yaml</code> file only needs to be on
servers where that command is run.</p>
<h3 id="sensitive-configuration-values">Sensitive Configuration Values</h3>
<p>Accumulo has a number of properties that can be specified via the <a
href="/docs/4.x/configuration/files#accumuloproperties">accumulo.properties</a>
-file which are sensitive in nature, <a
href="/docs/4.x/configuration/server-properties#instance_secret">instance.secret</a>
and <code class="language-plaintext
highlighter-rouge">trace.token.property.password</code>
-are two common examples. Both of these properties, if compromised, have the
ability
-to result in data being leaked to users who should not have access to that
data.</p>
+file which are sensitive in nature, <a
href="/docs/4.x/configuration/server-properties#instance_secret">instance.secret</a>
is an example. These sensitive properties,
+if compromised, have the ability to result in data being leaked to users who
should not have access to that data.</p>
<p>In Hadoop-2.6.0, a new CredentialProvider class was introduced which serves
as a common
implementation to abstract away the storage and retrieval of passwords from
plaintext
@@ -791,51 +800,36 @@ consideration. There is no enforcement of these warnings
via the API.</p>
<p>Accumulo builds its Java classpath in <a
href="/docs/4.x/configuration/files#accumulo-envsh">accumulo-env.sh</a>. This
classpath can be viewed by running
<code class="language-plaintext highlighter-rouge">accumulo
classpath</code>.</p>
-<p>After an Accumulo application has started, it will load classes from the
locations specified in the
-deprecated <a
href="/docs/4.x/configuration/server-properties#general_classpaths">general.classpaths</a>
property. Additionally, Accumulo will load classes from the
-locations specified in the <a
href="/docs/4.x/configuration/server-properties#general_dynamic_classpaths">general.dynamic.classpaths</a>
property and will monitor and reload them if
-they change. The reloading feature is useful during the development and
testing of iterators as new
-or modified iterator classes can be deployed to Accumulo without having to
restart the database.</p>
-
-<p>Accumulo also has an alternate configuration for the classloader which will
allow it to load classes
-from remote locations. This mechanism uses Apache Commons VFS which enables
locations such as http
-and hdfs to be used. This alternate configuration also uses the <a
href="/docs/4.x/configuration/server-properties#general_classpaths">general.classpaths</a>
property in the
-same manner described above. It differs in that you need to configure the <a
href="/docs/4.x/configuration/server-properties#general_vfs_classpaths">general.vfs.classpaths</a>
-property instead of the <a
href="/docs/4.x/configuration/server-properties#general_dynamic_classpaths">general.dynamic.classpaths</a>
property. As in the default configuration, this
-alternate configuration will also monitor the vfs locations for changes and
reload if necessary.</p>
-
<h5 id="classloader-contexts">ClassLoader Contexts</h5>
-<p>With the addition of the VFS based classloader, we introduced the notion of
classloader contexts. A
-context is identified by a name and references a set of locations from which
to load classes and can
-be specified in the <a
href="/docs/4.x/configuration/files#accumuloproperties">accumulo.properties</a>
file or added using the <code class="language-plaintext
highlighter-rouge">config</code> command in the shell.
-Below is an example for specify the app1 context in the <a
href="/docs/4.x/configuration/files#accumuloproperties">accumulo.properties</a>
file:</p>
-
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code># Application A classpath, loads jars from HDFS and
local file system
-general.vfs.context.classpath.app1=hdfs://localhost:8020/applicationA/classpath/.*.jar,file:///opt/applicationA/lib/.*.jar
-</code></pre></div></div>
-
-<p>The default behavior follows the Java ClassLoader contract in that classes,
if they exist, are
-loaded from the parent classloader first. You can override this behavior by
delegating to the parent
-classloader after looking in this classloader first. An example of this
configuration is:</p>
+<p>Tables can be configured to use a context classloader to load classes from
locations other
+than the server classpath. This enables users to deploy jars for their
application external
+to the server classpath allowing them to effect a classpath change without
restarting the Accumulo process.
+The property <code class="language-plaintext
highlighter-rouge">general.context.class.loader.factory</code> allows the user
to supply their own
+ContextClassLoaderFactory implementation.</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>general.vfs.context.classpath.app1.delegation=post
-</code></pre></div></div>
-
-<p>To use contexts in your application you can set the <a
href="/docs/4.x/configuration/server-properties#table_classpath_context">table.classpath.context</a>
on your
+<p>To use contexts in your application you can set the <a
href="/docs/4.x/configuration/server-properties#table_class_loader_context">table.class.loader.context</a>
on your
tables or use the <code class="language-plaintext
highlighter-rouge">setClassLoaderContext()</code> method on Scanner and
BatchScanner passing in the name
-of the context, app1 in the example above. Setting the property on the table
allows your minc, majc,
+of the context. Setting the property on the table allows your minc, majc,
and scan iterators to load classes from the locations defined by the context.
Passing the context
name to the scanners allows you to override the table setting to load only
scan time iterators from
a different location.</p>
+<p>The default ContextClassLoaderFactory implementation,
URLContextClassLoaderFactory, uses
+a comma-separated list of jar paths as the context name and returns a
URLClassLoader using
+the same paths. For example, to use the default implementation you would set
the
+<a
href="/docs/4.x/configuration/server-properties#table_class_loader_context">table.class.loader.context</a>
property to <code class="language-plaintext
highlighter-rouge">file://path/one/jar1.jar,file://path/two/jar2.jar</code></p>
+
+<p>An alternate ContextClassLoaderFactory implementation that supports
additional features
+can be found at
https://github.com/apache/accumulo-classloaders/tree/main/modules/caching-classloader.</p>
+
<h2 id="initialization">Initialization</h2>
<p>Accumulo must be initialized to create the structures it uses internally to
locate
data across the cluster. HDFS is required to be configured and running before
Accumulo can be initialized.</p>
-<p>Once HDFS is started, initialization can be performed by executing <code
class="language-plaintext highlighter-rouge">accumulo init</code>. This script
will
+<p>Once HDFS is started, initialization can be performed by executing <code
class="language-plaintext highlighter-rouge">accumulo inst init</code>. This
script will
prompt for a name for this instance of Accumulo. The instance name is used to
identify a set of
tables and instance-specific settings. The script will then write some
information into HDFS so
Accumulo can start properly.</p>
@@ -851,7 +845,7 @@ can be started.</p>
HDFS instance. Make sure HDFS and ZooKeeper are running. Make sure ZooKeeper
is configured and
running on at least one machine in the cluster. Start Accumulo using <code
class="language-plaintext highlighter-rouge">accumulo-cluster start</code>.</p>
-<p>To verify that Accumulo is running, check the <a
href="/docs/4.x/administration/monitoring-metrics#monitor">Accumulo
monitor</a>. In addition, the Shell
+<p>To verify that Accumulo is running, check the <a
href="/docs/4.x/administration/monitoring-metrics#accumulo-monitor">Accumulo
monitor</a>. In addition, the Shell
can provide some information about the status of tables via reading the
metadata tables.</p>
<h3 id="stopping-accumulo">Stopping Accumulo</h3>
@@ -864,7 +858,7 @@ take some time for particular configurations.</p>
<p>Update your <code class="language-plaintext
highlighter-rouge">conf/cluster.yaml</code> file to account for the
addition.</p>
-<p>Next, ssh to each of the hosts you want to add and run:</p>
+<p>Next, run <code class="language-plaintext
highlighter-rouge">accumulo-cluster start</code> or ssh to each of the hosts
you want to add and run:</p>
<div class="language-bash highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>accumulo-service tserver start
</code></pre></div></div>
@@ -878,7 +872,7 @@ but in practice it’s good to ensure consistent
configuration across all nodes.
<p>If you need to take a node out of operation, you can trigger a graceful
shutdown of a tablet
server. Accumulo will automatically rebalance the tablets across the available
tablet servers.</p>
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>accumulo admin stop <host<span
class="o">(</span>s<span class="o">)></span> <span
class="o">{</span><host> ...<span class="o">}</span>
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>accumulo proc stop-servers <host:port> <span
class="o">{</span><host:port> ...<span class="o">}</span>
</code></pre></div></div>
<p>Alternatively, you can ssh to each of the hosts you want to remove and
run:</p>
@@ -886,10 +880,7 @@ server. Accumulo will automatically rebalance the tablets
across the available t
<div class="language-bash highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>accumulo-service tserver stop
</code></pre></div></div>
-<p>Be sure to update your <code class="language-plaintext
highlighter-rouge">conf/cluster.yaml</code> file to account for the removal of
these hosts. Bear in mind
-that the monitor will not re-read the tservers file automatically, so it will
report the
-decommissioned servers as down; it’s recommended that you restart the monitor
so that the node list
-is up to date.</p>
+<p>Be sure to update your <code class="language-plaintext
highlighter-rouge">conf/cluster.yaml</code> file to account for the removal of
these hosts.</p>
<p>The steps described to decommission a node can also be used (without
removal of the host from the
<code class="language-plaintext highlighter-rouge">conf/cluster.yaml</code>
file) to gracefully stop a node. This will ensure that the tabletserver is
cleanly
@@ -931,45 +922,15 @@ to be able to scale to using 10’s of GB of RAM and 10’s
of CPU cores.</p>
<p>Accumulo TabletServers bind certain ports on the host to accommodate remote
procedure calls to/from
other nodes. Running more than one TabletServer on a host requires that you
set the environment
-variable <code class="language-plaintext
highlighter-rouge">ACCUMULO_SERVICE_INSTANCE</code> to an instance number (i.e
1, 2) for each instance that is
-started. Also, set the these properties in <a
href="/docs/4.x/configuration/files#accumuloproperties">accumulo.properties</a>:</p>
-
-<ul>
- <li><a
href="/docs/4.x/configuration/server-properties#tserver_port_search">tserver.port.search</a>
= <code class="language-plaintext highlighter-rouge">true</code></li>
- <li><a
href="/docs/4.x/configuration/server-properties#replication_receipt_service_port">replication.receipt.service.port</a>
= <code class="language-plaintext highlighter-rouge">0</code></li>
-</ul>
-
-<p>In order to start multiple TabletServers on a node, the <code
class="language-plaintext highlighter-rouge">accumulo</code> command must be
used:</p>
+variable <code class="language-plaintext
highlighter-rouge">ACCUMULO_CLUSTER_ARG</code> to the number of processes
before starting the service with the
+<code class="language-plaintext highlighter-rouge">accumulo-service</code>
command. For example:</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>ACCUMULO_SERVICE_INSTANCE=1 ./bin/accumulo tserver
&> ./logs/tserver1.out &
-ACCUMULO_SERVICE_INSTANCE=2 ./bin/accumulo tserver &>
./logs/tserver2.out &
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>ACCUMULO_CLUSTER_ARG=2 ./bin/accumulo-service tserver
start
</code></pre></div></div>
-<h4
id="running-multiple-tabletservers-per-node-in-accumulo-210-and-later">Running
multiple TabletServers per node in Accumulo 2.1.0 and later</h4>
-<p>Starting with Accumulo 2.1.0, the <code class="language-plaintext
highlighter-rouge">accumulo-cluster</code> script can be used along with
environment
-variable <code class="language-plaintext
highlighter-rouge">NUM_TSERVERS</code> as a convenient alternative to the <code
class="language-plaintext highlighter-rouge">accumulo</code> command to start /
stop
-multiple TabletServers per node. For example, the following commands can be
used to start / stop
-2 TabletServers on the current node:</p>
-
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>NUM_TSERVERS=2 ./bin/accumulo-cluster start-here
-NUM_TSERVERS=2 ./bin/accumulo-cluster stop-here
-</code></pre></div></div>
-
-<p>To start / stop the entire Accumulo cluster with 2 TabletServers per worker
node, use:</p>
-
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>NUM_TSERVERS=2 ./bin/accumulo-cluster start
-NUM_TSERVERS=2 ./bin/accumulo-cluster stop
-</code></pre></div></div>
-
-<p>Other commands like <code class="language-plaintext
highlighter-rouge">accumulo-cluster start-tservers</code> and <code
class="language-plaintext highlighter-rouge">accumulo-cluster
stop-tservers</code> support
-the use of <code class="language-plaintext
highlighter-rouge">NUM_TSERVERS</code> to specify the number of TabletServers
per worker node.</p>
-
-<p>When <code class="language-plaintext
highlighter-rouge">accumulo-cluster</code> is used along with <code
class="language-plaintext highlighter-rouge">NUM_TSERVERS</code> greater than
1, the resultant log files
-and redirected stdout / stderr files for each TabletServer running on the node
have the instance
-number as part of their respective filenames.</p>
-
-<p>Lastly, starting with Accumulo 2.1.0 the <code class="language-plaintext
highlighter-rouge">accumulo-env.sh</code> script ensures that Accumulo metrics
-are correctly associated with the respective instance number for each
TabletServer on a node.</p>
+<h4 id="running-multiple-processes-per-node-with-accumulo-cluster">Running
multiple processes per node with accumulo-cluster</h4>
+<p>The <code class="language-plaintext
highlighter-rouge">accumulo-cluster</code> script supports starting multiple
processes on the same node. See
+the scripts help output for more information.</p>
<h2 id="logging">Logging</h2>
@@ -992,10 +953,10 @@ either when the tablets from the failed server are
reassigned by the Manager (in
case of a single TabletServer failure) or the next time Accumulo starts (in
the event of
failure during shutdown).</p>
-<p>Recovery is performed by asking a tablet server to sort the logs so that
tablets can easily find
-their missing updates. The sort status of each file is displayed on Accumulo
monitor status page.
-Once the recovery is complete any tablets involved should return to an <code
class="language-plaintext highlighter-rouge">online</code> state. Until then
-those tablets will be unavailable to clients.</p>
+<p>Recovery is performed by asking a compactor, scan server, or tablet server
processes to sort the
+logs so that tablets can easily find their missing updates. The sort status of
each file is
+displayed on Accumulo monitor status page. Once the recovery is complete any
tablets involved
+should return to an <code class="language-plaintext
highlighter-rouge">online</code> state. Until then those tablets will be
unavailable to clients.</p>
<p>The Accumulo client library is configured to retry failed mutations and in
many
cases clients will be able to continue processing after the recovery process
without
@@ -1006,7 +967,7 @@ throwing an exception.</p>
<p>The following steps will allow a non-HA instance to be migrated to an HA
instance. Consider an HDFS
URL <code class="language-plaintext
highlighter-rouge">hdfs://namenode.example.com:8020</code> which is going to be
moved to <code class="language-plaintext
highlighter-rouge">hdfs://nameservice1</code>.</p>
-<p>Before moving HDFS over to the HA namenode, use <code
class="language-plaintext highlighter-rouge">accumulo admin volumes</code> to
confirm
+<p>Before moving HDFS over to the HA namenode, use <code
class="language-plaintext highlighter-rouge">accumulo inst list-volumes</code>
to confirm
that the only volume displayed is the volume from the current namenode’s HDFS
URL.</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>Listing volumes referenced in zookeeper
@@ -1035,8 +996,8 @@ instance.volumes=hdfs://nameservice1/accumulo
instance.volumes.replacements=hdfs://namenode.example.com:8020/accumulo
hdfs://nameservice1/accumulo
</code></pre></div></div>
-<p>Run <code class="language-plaintext highlighter-rouge">accumulo init
--add-volumes</code> and start up the accumulo cluster. Verify that the
-new nameservice volume shows up with <code class="language-plaintext
highlighter-rouge">accumulo admin volumes</code>.</p>
+<p>Run <code class="language-plaintext highlighter-rouge">accumulo inst init
--add-volumes</code> and start up the accumulo cluster. Verify that the
+new nameservice volume shows up with <code class="language-plaintext
highlighter-rouge">accumulo inst list-volumes</code>.</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>Listing volumes referenced in zookeeper
Volume : hdfs://namenode.example.com:8020/accumulo
diff --git a/output/feed.xml b/output/feed.xml
index d4648463c..8205ac078 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>Mon, 28 Sep 2026 20:23:08 +0000</pubDate>
- <lastBuildDate>Mon, 28 Sep 2026 20:23:08 +0000</lastBuildDate>
+ <pubDate>Tue, 29 Sep 2026 19:00:07 +0000</pubDate>
+ <lastBuildDate>Tue, 29 Sep 2026 19:00:07 +0000</lastBuildDate>
<generator>Jekyll v4.4.1</generator>
