This is an automated email from the ASF dual-hosted git repository.
git-site-role 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 00ed6702 Automatic Site Publish by Buildbot
00ed6702 is described below
commit 00ed67027b1dbb41bd694b96ddef2d3c04e63c02
Author: buildbot <us...@infra.apache.org>
AuthorDate: Tue Dec 19 15:11:00 2023 +0000
Automatic Site Publish by Buildbot
---
output/docs/2.x/administration/in-depth-install.html | 18 ++++++------------
output/docs/2.x/administration/upgrading.html | 2 +-
output/feed.xml | 4 ++--
output/search_data.json | 2 +-
4 files changed, 10 insertions(+), 16 deletions(-)
diff --git a/output/docs/2.x/administration/in-depth-install.html
b/output/docs/2.x/administration/in-depth-install.html
index 960acfe0..29215e6a 100644
--- a/output/docs/2.x/administration/in-depth-install.html
+++ b/output/docs/2.x/administration/in-depth-install.html
@@ -475,11 +475,6 @@ their value in <a
href="/docs/2.x/configuration/files#accumuloproperties">accumu
<td>Shutdown Port (Accumulo MiniCluster)</td>
<td>n/a</td>
</tr>
- <tr>
- <td>4560</td>
- <td>Accumulo monitor (for centralized log display)</td>
- <td><a
href="/docs/2.x/configuration/server-properties#monitor_port_log4j">monitor.port.log4j</a></td>
- </tr>
<tr>
<td>9132</td>
<td>Accumulo Compaction Coordinator</td>
@@ -498,7 +493,7 @@ their value in <a
href="/docs/2.x/configuration/files#accumuloproperties">accumu
<tr>
<td>9996</td>
<td>Accumulo Scan Server</td>
- <td>[sserver.port.client]</td>
+ <td><a
href="/docs/2.x/configuration/server-properties#sserver_port_client">sserver.port.client</a></td>
</tr>
<tr>
<td>9997</td>
@@ -592,9 +587,8 @@ manually or run <code class="language-plaintext
highlighter-rouge">accumulo-clus
<p>Logging is configured in <a
href="/docs/2.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
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/2.x/configuration/files#log4j-serviceproperties">log4j-service.properties</a>
except for
-the Monitor which is configured by <a
href="/docs/2.x/configuration/files#log4j-monitorproperties">log4j-monitor.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/2.x/configuration/files#log4jproperties">log4j.properties</a>.</p>
+(i.e. Manager, TabletServer, Garbage Collector) is configured by <a
href="/docs/2.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/2.x/configuration/files#log4j2properties">log4j2.properties</a>.</p>
<h3 id="configure-accumulo-envsh">Configure accumulo-env.sh</h3>
@@ -702,9 +696,9 @@ machine that will serve as the Accumulo manager:</p>
<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/2.x/configuration/files#managers">manager</a> section.</li>
+ <li>Write the IP address or domain name of the Accumulo Manager to the <a
href="/docs/2.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/2.x/configuration/files#tservers">tserver</a> section.</li>
+<a href="/docs/2.x/configuration/files#tserver">tserver</a> section.</li>
</ol>
<p>Note that if using domain names rather than IP addresses, DNS must be
configured
@@ -1007,7 +1001,7 @@ set by <code class="language-plaintext
highlighter-rouge">ACCUMULO_LOG_DIR</code
<p>Accumulo logs many user-initiated actions, and whether they succeeded or
failed, to an slf4j logger
named <code class="language-plaintext
highlighter-rouge">org.apache.accumulo.audit</code>. This logger can be
configured in the user’s logging framework
-(such as log4j or logback). In the tarball, the configuration file <code
class="language-plaintext
highlighter-rouge">conf/log4j-service.properties</code>
+(such as log4j or logback). In the tarball, the configuration file <code
class="language-plaintext
highlighter-rouge">conf/log4j2-service.properties</code>
demonstrates basic audit logging with example configuration options for
log4j.</p>
<h2 id="recovery">Recovery</h2>
diff --git a/output/docs/2.x/administration/upgrading.html
b/output/docs/2.x/administration/upgrading.html
index 008acdb5..a1999e20 100644
--- a/output/docs/2.x/administration/upgrading.html
+++ b/output/docs/2.x/administration/upgrading.html
@@ -449,7 +449,7 @@ this writing and is recommended).</p>
configure it in your environment</li>
<li>start ZooKeeper and HDFS.</li>
<li>(optional - but recommended) create a ZooKeeper snapshot</li>
- <li>(optional - but recommended) validate the ZooKeeper ACLs. See <a
href="/docs/2.x/troubleshooting/ZooKeeper#ACLs">ZooKeeper ACLs</a></li>
+ <li>(optional - but recommended) validate the ZooKeeper ACLs. See <a
href="/docs/2.x/troubleshooting/zookeeper#zookeeper-acls">ZooKeeper
ACLs</a></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>
diff --git a/output/feed.xml b/output/feed.xml
index 23be9a16..165e1594 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, 18 Dec 2023 17:39:10 +0000</pubDate>
- <lastBuildDate>Mon, 18 Dec 2023 17:39:10 +0000</lastBuildDate>
+ <pubDate>Tue, 19 Dec 2023 15:10:53 +0000</pubDate>
+ <lastBuildDate>Tue, 19 Dec 2023 15:10:53 +0000</lastBuildDate>
<generator>Jekyll v4.3.2</generator>
diff --git a/output/search_data.json b/output/search_data.json
index 4e178778..28e762ea 100644
--- a/output/search_data.json
+++ b/output/search_data.json
@@ -30,7 +30,7 @@
"docs-2-x-administration-in-depth-install": {
"title": "In-depth Installation",
- "content": "This document provides detailed instructions for installing
Accumulo. For basicinstructions, see the quick start.HardwareBecause we are
running essentially two or three systems simultaneously layeredacross the
cluster: HDFS, Accumulo and MapReduce, it is typical for hardware toconsist of
4 to 8 cores, and 8 to 32 GB RAM. This is so each running process can haveat
least one core and 2 - 4 GB each.One core running HDFS can typically keep 2 to
4 disks busy, so each machine [...]
+ "content": "This document provides detailed instructions for installing
Accumulo. For basicinstructions, see the quick start.HardwareBecause we are
running essentially two or three systems simultaneously layeredacross the
cluster: HDFS, Accumulo and MapReduce, it is typical for hardware toconsist of
4 to 8 cores, and 8 to 32 GB RAM. This is so each running process can haveat
least one core and 2 - 4 GB each.One core running HDFS can typically keep 2 to
4 disks busy, so each machine [...]
"url": " /docs/2.x/administration/in-depth-install",
"categories": "administration"
},
