Author: buildbot
Date: Tue Feb 9 20:51:32 2016
New Revision: 979967
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/1.6/accumulo_user_manual.html
Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 9 20:51:32 2016
@@ -1 +1 @@
-1725641
+1729455
Modified: websites/staging/accumulo/trunk/content/1.6/accumulo_user_manual.html
==============================================================================
--- websites/staging/accumulo/trunk/content/1.6/accumulo_user_manual.html
(original)
+++ websites/staging/accumulo/trunk/content/1.6/accumulo_user_manual.html Tue
Feb 9 20:51:32 2016
@@ -598,6 +598,7 @@ span.icon > [class^="icon-"], span.icon
<li><a href="#_adding_a_node">13.7.3. Adding a Node</a></li>
<li><a href="#_decomissioning_a_node">13.7.4. Decomissioning a Node</a></li>
<li><a href="#_restarting_process_on_a_node">13.7.5. Restarting process on a
node</a></li>
+<li><a href="#_running_multiple_tabletservers_on_a_single_node">13.7.6.
Running multiple TabletServers on a single node</a></li>
</ul>
</li>
<li><a href="#_monitoring">13.8. Monitoring</a></li>
@@ -1533,7 +1534,7 @@ BatchScanner bscan =
bscan.setRanges(ranges);
bscan.fetchColumnFamily(new Text("attributes"));
-for(Entry<Key,Value> entry : scan) {
+for(Entry<Key,Value> entry : bscan) {
System.out.println(entry.getValue());
}</code></pre>
</div>
@@ -4568,6 +4569,75 @@ when the tablets are re-hosted.</p>
</div>
</div>
+<div class="sect3">
+<h4 id="_running_multiple_tabletservers_on_a_single_node">13.7.6. Running
multiple TabletServers on a single node</h4>
+<div class="paragraph">
+<p>With very powerful nodes, it may be beneficial to run more than one
TabletServer on a given
+node. This decision should be made carefully and with much deliberation as
Accumulo is designed
+to be able to scale to using 10's of GB of RAM and 10's of CPU cores.</p>
+</div>
+
+<div class="paragraph">
+<p>To run multiple TabletServers on a single host, it is necessary to create
multiple Accumulo configuration
+directories. Ensuring that these properties are appropriately set (and remain
consistent) are an exercise
+for the user.</p>
+</div>
+
+<div class="paragraph">
+<p>Accumulo TabletServers bind certain ports on the host to accommodate remote
procedure calls to/from
+other nodes. This requires additional configuration values in
<code>accumulo-site.xml</code>:</p>
+</div>
+
+<div class="ulist">
+<ul>
+<li>
+<p>tserver.port.client</p>
+</li>
+</ul>
+</div>
+
+<div class="paragraph">
+<p>Normally, setting a value of <code>0</code> for these configuration
properties is sufficient. In some
+environment, the ports used by Accumulo must be well-known for security
reasons and require a
+separate copy of the configuration files to use a static port for each
TabletServer instance.</p>
+</div>
+
+<div class="paragraph">
+<p>It is also necessary to update the following exported variables in
<code>accumulo-env.sh</code>.</p>
+</div>
+
+<div class="ulist">
+<ul>
+<li>
+<p>ACCUMULO_LOG_DIR</p>
+</li>
+</ul>
+</div>
+
+<div class="paragraph">
+<p>The values for these properties are left up to the user to define; there
are no constraints
+other than ensuring that the directory exists and the user running Accumulo
has the permission
+to read/write into that directory.</p>
+</div>
+
+<div class="paragraph">
+<p>Accumulo's provided scripts for stopping a cluster operate under the
assumption that one process
+is running per host. As such, starting and stopping multiple TabletServers on
one host requires
+more effort on the user. It is important to ensure that
<code>ACCUMULO_CONF_DIR</code> is correctly
+set for the instance of the TabletServer being started.</p>
+</div>
+
+<div class="paragraph">
+<p><code>$ACCUMULO_CONF_DIR=$ACCUMULO_HOME/conf $ACCUMULO_HOME/bin/accumulo
tserver --address <your_server_ip> &</code></p>
+</div>
+
+<div class="paragraph">
+<p>To stop TabletServers, the normal <code>stop-all.sh</code> will stop all
instances of TabletServers across all nodes.
+Using the provided <code>kill</code> command by your operation system is an
option to stop a single instance on
+a single node. <code>stop-server.sh</code> can be used to stop all
TabletServers on a single node.</p>
+</div>
+</div>
+
<div class="sect2">
<h3 id="_monitoring">13.8. Monitoring</h3>
<div class="paragraph">
@@ -7740,7 +7810,7 @@ An example is <em>java.lang.String</em>,
</div>
<div id="footer">
<div id="footer-text">
-Last updated 2015-02-16 14:08:06 EST
+Last updated 2016-02-09 15:30:00 EST
</div>
</div>
</body>
