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 79f13fd Automatic Site Publish by Buildbot
79f13fd is described below
commit 79f13fdc39ff43c0061a4bf149441c44b5d7daff
Author: buildbot <[email protected]>
AuthorDate: Mon Apr 6 16:06:38 2020 +0000
Automatic Site Publish by Buildbot
---
.../docs/2.x/administration/in-depth-install.html | 29 ++++++++++++++++++++--
output/feed.xml | 4 +--
output/search_data.json | 2 +-
3 files changed, 30 insertions(+), 5 deletions(-)
diff --git a/output/docs/2.x/administration/in-depth-install.html
b/output/docs/2.x/administration/in-depth-install.html
index 9ff9703..e85388c 100644
--- a/output/docs/2.x/administration/in-depth-install.html
+++ b/output/docs/2.x/administration/in-depth-install.html
@@ -939,13 +939,38 @@ started. Also, set the these properties in <a
href="/docs/2.x/configuration/file
<li><a
href="/docs/2.x/configuration/server-properties#replication_receipt_service_port">replication.receipt.service.port</a>
= <code class="highlighter-rouge">0</code></li>
</ul>
-<p>Multiple TabletServers cannot be started using the <code
class="highlighter-rouge">accumulo-cluster</code> or <code
class="highlighter-rouge">accumulo-service</code> commands
-at this time. The <code class="highlighter-rouge">accumulo</code> command must
be used:</p>
+<p>In order to start multiple TabletServers on a node, the <code
class="highlighter-rouge">accumulo</code> command must be used:</p>
<div class="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 &
</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="highlighter-rouge">accumulo-cluster</code> script can be used along with
environment
+variable <code class="highlighter-rouge">NUM_TSERVERS</code> as a convenient
alternative to the <code class="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="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="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="highlighter-rouge">accumulo-cluster
start-tservers</code> and <code class="highlighter-rouge">accumulo-cluster
stop-tservers</code> support
+the use of <code class="highlighter-rouge">NUM_TSERVERS</code> to specify the
number of TabletServers per worker node.</p>
+
+<p>When <code class="highlighter-rouge">accumulo-cluster</code> is used along
with <code class="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="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>
+
<h2 id="logging">Logging</h2>
<p>Accumulo processes each write to a set of log files. By default, these logs
are found at directory
diff --git a/output/feed.xml b/output/feed.xml
index 1115c9e..8e9d9c6 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>Fri, 03 Apr 2020 18:10:53 +0000</pubDate>
- <lastBuildDate>Fri, 03 Apr 2020 18:10:53 +0000</lastBuildDate>
+ <pubDate>Mon, 06 Apr 2020 16:06:32 +0000</pubDate>
+ <lastBuildDate>Mon, 06 Apr 2020 16:06:32 +0000</lastBuildDate>
<generator>Jekyll v4.0.0</generator>
diff --git a/output/search_data.json b/output/search_data.json
index 96b0b38..9f474b8 100644
--- a/output/search_data.json
+++ b/output/search_data.json
@@ -23,7 +23,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 machi [...]
+ "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 machi [...]
"url": " /docs/2.x/administration/in-depth-install",
"categories": "administration"
},
