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 af63c872 Automatic Site Publish by Buildbot
af63c872 is described below
commit af63c872f614ba8085ec814831564714a969ef9d
Author: buildbot <us...@infra.apache.org>
AuthorDate: Wed Nov 2 04:51:41 2022 +0000
Automatic Site Publish by Buildbot
---
.../docs/2.x/administration/in-depth-install.html | 48 +++++++++++-----------
output/docs/2.x/configuration/files.html | 3 +-
output/feed.xml | 4 +-
output/search_data.json | 4 +-
4 files changed, 29 insertions(+), 30 deletions(-)
diff --git a/output/docs/2.x/administration/in-depth-install.html
b/output/docs/2.x/administration/in-depth-install.html
index 34a5f4d3..f6409616 100644
--- a/output/docs/2.x/administration/in-depth-install.html
+++ b/output/docs/2.x/administration/in-depth-install.html
@@ -551,9 +551,9 @@ at the low end of the range to, and including, the high end
of the range.</p>
<p>Download a binary distribution of Accumulo and install it to a directory on
a disk with
sufficient space:</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>cd <install directory>
-tar xzf accumulo-2.1.0-bin.tar.gz
-cd accumulo-2.1.0
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="nb">cd</span> <<span class="nb">install
</span>directory>
+<span class="nb">tar </span>xzf accumulo-2.1.0-bin.tar.gz
+<span class="nb">cd </span>accumulo-2.1.0
</code></pre></div></div>
<p>Repeat this step on each machine in your cluster. Typically, the same <code
class="language-plaintext highlighter-rouge"><install directory></code>
@@ -650,8 +650,8 @@ architecture. These will be passed to the Makefile in the
environment variable <
<p>Examples:</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>accumulo-util build-native
-accumulo-util build-native -m32
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>accumulo-util build-native
+accumulo-util build-native <span class="nt">-m32</span>
</code></pre></div></div>
<p>After building the native map from the source, you will find the artifact in
@@ -892,7 +892,7 @@ take some time for particular configurations.</p>
<p>Next, ssh to each of the hosts you want to add and run:</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>accumulo-service tserver start
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>accumulo-service tserver start
</code></pre></div></div>
<p>Make sure the host in question has the new configuration, or else the tablet
@@ -904,12 +904,12 @@ 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-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>accumulo admin stop <host(s)> {<host> ...}
+<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>
</code></pre></div></div>
<p>Alternatively, you can ssh to each of the hosts you want to remove and
run:</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>accumulo-service tserver stop
+<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
@@ -1036,14 +1036,14 @@ URL <code class="language-plaintext
highlighter-rouge">hdfs://namenode.example.c
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
- Volume : hdfs://namenode.example.com:8020/accumulo
+ Volume : hdfs://namenode.example.com:8020/accumulo
Listing volumes referenced in accumulo.root tablets section
- Volume : hdfs://namenode.example.com:8020/accumulo
+ Volume : hdfs://namenode.example.com:8020/accumulo
Listing volumes referenced in accumulo.root deletes section (volume
replacement occurs at deletion time)
Listing volumes referenced in accumulo.metadata tablets section
- Volume : hdfs://namenode.example.com:8020/accumulo
+ Volume : hdfs://namenode.example.com:8020/accumulo
Listing volumes referenced in accumulo.metadata deletes section (volume
replacement occurs at deletion time)
</code></pre></div></div>
@@ -1065,17 +1065,17 @@
instance.volumes.replacements=hdfs://namenode.example.com:8020/accumulo hdfs://n
new nameservice volume shows up with <code class="language-plaintext
highlighter-rouge">accumulo admin 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
- Volume : hdfs://nameservice1/accumulo
+ Volume : hdfs://namenode.example.com:8020/accumulo
+ Volume : hdfs://nameservice1/accumulo
Listing volumes referenced in accumulo.root tablets section
- Volume : hdfs://namenode.example.com:8020/accumulo
- Volume : hdfs://nameservice1/accumulo
+ Volume : hdfs://namenode.example.com:8020/accumulo
+ Volume : hdfs://nameservice1/accumulo
Listing volumes referenced in accumulo.root deletes section (volume
replacement occurs at deletion time)
Listing volumes referenced in accumulo.metadata tablets section
- Volume : hdfs://namenode.example.com:8020/accumulo
- Volume : hdfs://nameservice1/accumulo
+ Volume : hdfs://namenode.example.com:8020/accumulo
+ Volume : hdfs://nameservice1/accumulo
Listing volumes referenced in accumulo.metadata deletes section (volume
replacement occurs at deletion time)
</code></pre></div></div>
@@ -1156,13 +1156,13 @@ the memory.maps.max parameter in
accumulo.properties.</li>
Off-heap memory, plus the in-memory map of the Accumulo TServer process. A
simple calculation for physical memory requirements follows:</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code> Physical memory needed
- = (per-process off-heap memory) + (heap memory) + (other processes) +
(margin)
- = (number of java processes * 150M + native map) + (sum of -Xmx settings
for java process)
- + (total applications memory, provisioning memory, etc.) + (1G)
- = (11*150M +500M) + (1G +1G +1G +256M +1G +256M +512M +512M +512M +512M
+512M) + (2G) + (1G)
- = (2150M) + (7G) + (2G) + (1G)
- = ~12GB
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>Physical memory needed
+ = (per-process off-heap memory) + (heap memory) + (other processes) +
(margin)
+ = (number of java processes * 150M + native map) + (sum of -Xmx settings for
java process)
+ + (total applications memory, provisioning memory, etc.) + (1G)
+ = (11*150M +500M) + (1G +1G +1G +256M +1G +256M +512M +512M +512M +512M
+512M) + (2G) + (1G)
+ = (2150M) + (7G) + (2G) + (1G)
+ = ~12GB
</code></pre></div></div>
<p>These calculations can add up quickly with the large number of processes,
diff --git a/output/docs/2.x/configuration/files.html
b/output/docs/2.x/configuration/files.html
index 748e4c7d..de0bf067 100644
--- a/output/docs/2.x/configuration/files.html
+++ b/output/docs/2.x/configuration/files.html
@@ -449,8 +449,7 @@ configuring this file.</p>
the Accumulo connection information in this file will be used. This file can
be used to create an AccumuloClient
in Java using the following code:</p>
-<div class="language-java highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="nc">AccumuloClient</span> <span
class="n">client</span> <span class="o">=</span> <span
class="nc">Accumulo</span><span class="o">.</span><span
class="na">newClient</span><span class="o">()</span>
- <span class="o">.</span><span
class="na">from</span><span class="o">(</span><span
class="s">"/path/to/accumulo-client.properties"</span><span
class="o">).</span><span class="na">build</span><span class="o">();</span>
+<div class="language-java highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="nc">AccumuloClient</span> <span
class="n">client</span> <span class="o">=</span> <span
class="nc">Accumulo</span><span class="o">.</span><span
class="na">newClient</span><span class="o">().</span><span
class="na">from</span><span class="o">(</span><span
class="s">"/path/to/accumulo-client.properties"</span><span
class="o">).</span><span class="na">build</span><span class="o">();</span>
</code></pre></div></div>
<p>See the <a
href="/docs/2.x/getting-started/quickstart#configuring-accumulo">quick
start</a> for help with configuring this file.</p>
diff --git a/output/feed.xml b/output/feed.xml
index c6579c62..b034a747 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, 02 Nov 2022 04:44:44 +0000</pubDate>
- <lastBuildDate>Wed, 02 Nov 2022 04:44:44 +0000</lastBuildDate>
+ <pubDate>Wed, 02 Nov 2022 04:51:34 +0000</pubDate>
+ <lastBuildDate>Wed, 02 Nov 2022 04:51:34 +0000</lastBuildDate>
<generator>Jekyll v4.3.1</generator>
diff --git a/output/search_data.json b/output/search_data.json
index ba488af5..ff09ad28 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"
},
@@ -79,7 +79,7 @@
"docs-2-x-configuration-files": {
"title": "Configuration Files",
- "content": "Accumulo has the following configuration files which can be
found in theconf/ directory of the Accumulo release
tarball.accumulo.propertiesThe accumulo.properties file configures Accumulo
server processes usingserver properties. This file can be found in the
conf/direcory. It is needed on every host that runs Accumulo processes.
Therfore, any configuration should bereplicated to all hosts of the Accumulo
cluster. If a property is not configured here, it might have beenc [...]
+ "content": "Accumulo has the following configuration files which can be
found in theconf/ directory of the Accumulo release
tarball.accumulo.propertiesThe accumulo.properties file configures Accumulo
server processes usingserver properties. This file can be found in the
conf/direcory. It is needed on every host that runs Accumulo processes.
Therfore, any configuration should bereplicated to all hosts of the Accumulo
cluster. If a property is not configured here, it might have beenc [...]
"url": " /docs/2.x/configuration/files",
"categories": "configuration"
},
