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 8e5128f79 Automatic Site Publish by Buildbot
8e5128f79 is described below

commit 8e5128f7929201574ea48c4abbb02e840b05b334
Author: buildbot <[email protected]>
AuthorDate: Tue Sep 22 11:36:01 2026 +0000

    Automatic Site Publish by Buildbot
---
 output/docs/4.x/configuration/overview.html        | 29 +++++++++++-
 .../docs/4.x/configuration/server-properties.html  | 53 +++++++++++++++++++++-
 .../4.x/getting-started/table_configuration.html   |  4 ++
 output/feed.xml                                    |  4 +-
 4 files changed, 86 insertions(+), 4 deletions(-)

diff --git a/output/docs/4.x/configuration/overview.html 
b/output/docs/4.x/configuration/overview.html
index 966ff9c7a..98ab01552 100644
--- a/output/docs/4.x/configuration/overview.html
+++ b/output/docs/4.x/configuration/overview.html
@@ -425,11 +425,13 @@ set in the following configuration locations (with 
increasing precedence):</p>
   <li><a href="#default">Default</a> - All properties have a default value</li>
   <li><a href="#site">Site</a> - Properties set in <a 
href="/docs/4.x/configuration/files#accumuloproperties">accumulo.properties</a></li>
   <li><a href="#system">System</a> - Properties set using shell or Java API 
that apply to entire Accumulo instance</li>
+  <li><a href="#resourcegroup">Resource Group</a> - Property set using the 
shell or Java API that apply to processes in a Resource Group</li>
   <li><a href="#namespace">Namespace</a> - Table properties set using shell or 
Java API that apply to a table namespace</li>
   <li><a href="#table">Table</a> - Table properties set using shell or Java 
API that apply to a table.</li>
 </ol>
 
-<p>If a property is set in multiple locations, the value in the location with 
the highest precedence is used.</p>
+<p>If a property is set in multiple locations, the value in the location with 
the highest precedence is used. Note that starting
+with 4.0.0 table properties can only be specified in Namespace and Table 
configuration locations.</p>
 
 <p>These configuration locations are described in detail below:</p>
 
@@ -475,6 +477,31 @@ the following shell command:</p>
 <span class="o">});</span>
 </code></pre></div></div>
 
+<h3 id="resourcegroup">ResourceGroup</h3>
+
+<p>Resource Group configuration refers to <a 
href="/docs/4.x/configuration/server-properties">server properties</a> set for 
the processes running in a Resource Group. These settings are stored in 
ZooKeeper and can be identified
+by <strong>zk mutable: yes</strong> in their description on the <a 
href="/docs/4.x/configuration/server-properties">server properties</a> page. 
Resource Group configuration will override any System configuration set in 
ZooKeeper and
+any site configuration set in <a 
href="/docs/4.x/configuration/files#accumuloproperties">accumulo.properties</a>.
 While most system configuration settings take effect immediately, some require 
a restart of the process which is
+indicated in the <strong>zk mutable</strong> section of their description. 
Resource Group configuration can be set using the following shell command:</p>
+
+<div class="language-console highlighter-rouge"><div class="highlight"><pre 
class="highlight"><code><span class="go">config -rg GROUP_NAME -s PROPERTY=VALUE
+</span></code></pre></div></div>
+
+<p>They can also be set using <a 
href="https://www.javadoc.io/static/org.apache.accumulo/accumulo-core/4.0.0-SNAPSHOT/org/apache/accumulo/core/client/admin/ResourceGroupOperations.html";>ResourceGroupOperations</a>
 in the Java API:</p>
+
+<div class="language-java highlighter-rouge"><div class="highlight"><pre 
class="highlight"><code><span class="n">client</span><span 
class="o">.</span><span class="na">resourceGroupOperations</span><span 
class="o">().</span><span class="na">setProperty</span><span 
class="o">(</span><span class="s">"general.low.mem.protection.scan"</span><span 
class="o">,</span> <span class="s">"true"</span><span class="o">);</span>
+</code></pre></div></div>
+
+<p>The java api also supports adding, modifying and removing multiple 
properties in a single operation:</p>
+
+<div class="language-java highlighter-rouge"><div class="highlight"><pre 
class="highlight"><code><span class="n">client</span><span 
class="o">.</span><span class="na">resourceGroupOperations</span><span 
class="o">().</span><span class="na">modifyProperties</span><span 
class="o">(</span><span class="n">properties</span> <span 
class="o">-&gt;</span> <span class="o">{</span>
+  <span class="n">properties</span><span class="o">.</span><span 
class="na">remove</span><span class="o">(</span><span 
class="s">"general.block.cache.manager.class"</span><span class="o">);</span>
+  <span class="n">properties</span><span class="o">.</span><span 
class="na">put</span><span class="o">(</span><span 
class="s">"general.low.mem.protection.scan"</span><span class="o">,</span> 
<span class="s">"true"</span><span class="o">);</span>
+  <span class="n">properties</span><span class="o">.</span><span 
class="na">put</span><span class="o">(</span><span 
class="s">"general.server.iter.opts.compression"</span><span class="o">,</span> 
<span class="s">"zstd"</span><span class="o">);</span>
+  <span class="n">properties</span><span class="o">.</span><span 
class="na">put</span><span class="o">(</span><span 
class="s">"tserver.summary.retrieval.threads"</span><span class="o">,</span> 
<span class="s">"128"</span><span class="o">);</span>
+<span class="o">});</span>
+</code></pre></div></div>
+
 <h3 id="namespace">Namespace</h3>
 
 <p>Namespace configuration refers to <a 
href="/docs/4.x/configuration/server-properties#table_prefix">table.* 
properties</a> set for a certain table namespace (i.e. group of tables). These 
settings are stored in ZooKeeper. Namespace configuration
diff --git a/output/docs/4.x/configuration/server-properties.html 
b/output/docs/4.x/configuration/server-properties.html
index cb353b0a7..ea3097de3 100644
--- a/output/docs/4.x/configuration/server-properties.html
+++ b/output/docs/4.x/configuration/server-properties.html
@@ -433,6 +433,10 @@
       <td><a name="compaction_coordinator_compactor_dead_check_interval" 
class="prop"></a> compaction.coordinator.compactor.dead.check.interval</td>
       <td><strong>Available since:</strong> 2.1.0<br />The interval at which 
to check for dead compactors.<br /><strong>type:</strong> TIMEDURATION, 
<strong>zk mutable:</strong> yes but requires restart of the compaction, 
<strong>default value:</strong> <code class="language-plaintext 
highlighter-rouge">5m</code></td>
     </tr>
+    <tr>
+      <td><a name="compaction_coordinator_compactor_wakeup_threads" 
class="prop"></a> compaction.coordinator.compactor.wakeup.threads</td>
+      <td><strong>Available since:</strong> 2.1.7<br />The number of threads 
the Coordinator should use to wake Compactors that are in a wait state. A value 
of zero disables Compactor wake up. Enabling this feature will cause Compactors 
in a long wait state (see COMPACTOR_MAX_JOB_WAIT_TIME) to check in with the 
Coordinator for work.<br /><strong>type:</strong> COUNT, <strong>zk 
mutable:</strong> yes, <strong>default value:</strong> <code 
class="language-plaintext highlighter-rouge">0</co [...]
+    </tr>
     <tr>
       <td><a name="compaction_coordinator_reservation_threads_meta" 
class="prop"></a> compaction.coordinator.reservation.threads.meta</td>
       <td><strong>Available since:</strong> 4.0.0<br />The number of threads 
used to reserve files for compaction in a tablet for accumulo.metadata 
tablets.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, 
<strong>default value:</strong> <code class="language-plaintext 
highlighter-rouge">1</code></td>
@@ -661,6 +665,10 @@
       <td><del><a name="general_process_bind_addr" class="prop"></a> 
general.process.bind.addr</del></td>
       <td><strong>Available since:</strong> 3.0.0<br /><em>Deprecated 
since:</em> 4.0.0<br /><em>Replaced by:</em> <a 
href="#rpc_bind_addr">rpc.bind.addr</a><br /><del>The local IP address to which 
this server should bind for sending and receiving network traffic.</del><br 
/><del><strong>type:</strong> STRING</del>, <del><strong>zk mutable:</strong> 
no</del>, <del><strong>default value:</strong> <code class="language-plaintext 
highlighter-rouge">0.0.0.0</code></del></td>
     </tr>
+    <tr>
+      <td><a name="general_rpc_server_threaded_selector_threads" 
class="prop"></a> general.rpc.server.threaded.selector.threads</td>
+      <td><strong>Available since:</strong> 2.1.7<br />The number of selector 
threads to use for the TThreadedSelectorServer.  If the value ends with C, then 
it will be multiplied by the number of cores on the system.<br 
/><strong>type:</strong> COUNT, <strong>zk mutable:</strong> no, 
<strong>default value:</strong> <code class="language-plaintext 
highlighter-rouge">2</code></td>
+    </tr>
     <tr>
       <td><a name="general_rpc_server_type" class="prop"></a> 
general.rpc.server.type</td>
       <td><strong>Experimental</strong><br /><strong>Available since:</strong> 
1.7.0<br />Type of Thrift server to instantiate, see 
org.apache.accumulo.server.rpc.ThriftServerType for more information. Only 
useful for benchmarking thrift servers.<br /><strong>type:</strong> STRING, 
<strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
@@ -1343,7 +1351,7 @@
     </tr>
     <tr>
       <td><a name="table_scan_max_memory" class="prop"></a> 
table.scan.max.memory</td>
-      <td><strong>Available since:</strong> 1.3.5<br />The maximum amount of 
memory that will be used to cache results of a client query/scan. Once this 
limit is reached, the buffered data is sent to the client.<br 
/><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, 
<strong>default value:</strong> <code class="language-plaintext 
highlighter-rouge">512k</code></td>
+      <td><strong>Available since:</strong> 1.3.5<br />The maximum amount of 
memory that will be used to cache results of a client query/scan. Once this 
limit is reached, the buffered data is sent to the client. This is an estimate 
of heap usage and includes per entry object overhead, so it will always exceed 
the size of the key value data actually sent to the client.<br 
/><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, 
<strong>default value:</strong> <code class="languag [...]
     </tr>
     <tr>
       <td><a name="table_security_scan_visibility_default" class="prop"></a> 
table.security.scan.visibility.default</td>
@@ -1701,6 +1709,49 @@
   </tbody>
 </table>
 
+<h3 id="java-system-properties">Java System Properties</h3>
+
+<p>Below are properties used to modify the runtime behavior.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Property</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>accumulo.properties</td>
+      <td>Path to accumulo.properties file.</td>
+    </tr>
+    <tr>
+      <td>io.compression.codec.bzip2.class</td>
+      <td>BZip2 Codec Compression Algorithm.</td>
+    </tr>
+    <tr>
+      <td>io.compression.codec.lz4.class</td>
+      <td>LZ4 Codec Compression Algorithm.</td>
+    </tr>
+    <tr>
+      <td>io.compression.codec.lzo.class</td>
+      <td>LZO Codec Compression Algorithm.</td>
+    </tr>
+    <tr>
+      <td>io.compression.codec.snappy.class</td>
+      <td>Snappy Codec Compression Algorithm.</td>
+    </tr>
+    <tr>
+      <td>io.compression.codec.zstd.class</td>
+      <td>ZStandard Codec Compression Algorithm.</td>
+    </tr>
+    <tr>
+      <td>org.apache.accumulo.client.rpc.debug.host</td>
+      <td>Set to host:port for the client to connect to a specific server.</td>
+    </tr>
+  </tbody>
+</table>
+
     <div class="row mt-4">
       <div class="col-md-12 d-flex justify-content-between">
         <strong>Find documentation for all releases in the <a 
href="/docs-archive">archive</strong>
diff --git a/output/docs/4.x/getting-started/table_configuration.html 
b/output/docs/4.x/getting-started/table_configuration.html
index 536a19934..a799723b7 100644
--- a/output/docs/4.x/getting-started/table_configuration.html
+++ b/output/docs/4.x/getting-started/table_configuration.html
@@ -749,6 +749,7 @@ in reduced read latency. Read the <a 
href="/docs/4.x/administration/caching">Cac
 <h2 id="compaction">Compaction</h2>
 
 <p>See <a href="/docs/4.x/administration/compaction">compaction </a></p>
+
 <h2 id="pre-splitting-tables">Pre-splitting tables</h2>
 
 <p>Accumulo will balance and distribute tables across servers. Before a
@@ -819,6 +820,9 @@ faster to set the split point and merge the entire 
table:</p>
 root@myinstance&gt; merge -t myTable
 </code></pre></div></div>
 
+<p>Automatic merging of tablets has been added in 4.0.0 and is described
+further in <a href="/docs/4.x/administration/merging">merging</a>.</p>
+
 <h2 id="delete-range">Delete Range</h2>
 
 <p>Consider an indexing scheme that uses date information in each row.
diff --git a/output/feed.xml b/output/feed.xml
index 315d9b46f..a795e928e 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>Tue, 22 Sep 2026 11:33:51 +0000</pubDate>
-    <lastBuildDate>Tue, 22 Sep 2026 11:33:51 +0000</lastBuildDate>
+    <pubDate>Tue, 22 Sep 2026 11:35:54 +0000</pubDate>
+    <lastBuildDate>Tue, 22 Sep 2026 11:35:54 +0000</lastBuildDate>
     <generator>Jekyll v4.4.1</generator>
     
     

Reply via email to