You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by mw...@apache.org on 2017/12/07 21:54:05 UTC
[accumulo-website] branch asf-site updated: Jekyll build from
master:269dfb4
This is an automated email from the ASF dual-hosted git repository.
mwalch 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 05af022 Jekyll build from master:269dfb4
05af022 is described below
commit 05af022a4093a8d1b493ae1d8b212d7a01d8057e
Author: Mike Walch <mw...@apache.org>
AuthorDate: Thu Dec 7 16:53:34 2017 -0500
Jekyll build from master:269dfb4
ACCUMULO-4754 Converted properties to links
* Also renamed configuration-properties.md to properties.md
---
contributor/making-release.html | 8 +-
css/accumulo.css | 3 +
docs/2.0/administration/caching.html | 10 +-
.../administration/configuration-management.html | 18 +-
docs/2.0/administration/fate.html | 2 +-
docs/2.0/administration/in-depth-install.html | 94 ++--
docs/2.0/administration/kerberos.html | 2 +-
docs/2.0/administration/monitoring-metrics.html | 24 +-
docs/2.0/administration/multivolume.html | 15 +-
...nfiguration-properties.html => properties.html} | 492 +++++++++++----------
docs/2.0/administration/replication.html | 2 +-
docs/2.0/administration/ssl.html | 25 +-
docs/2.0/administration/tracing.html | 34 +-
docs/2.0/administration/upgrading.html | 2 +-
docs/2.0/development/development_tools.html | 2 +-
docs/2.0/development/high_speed_ingest.html | 2 +-
docs/2.0/development/iterators.html | 2 +-
docs/2.0/development/mapreduce.html | 2 +-
docs/2.0/development/proxy.html | 2 +-
docs/2.0/development/sampling.html | 2 +-
docs/2.0/development/security.html | 2 +-
docs/2.0/development/summaries.html | 14 +-
docs/2.0/getting-started/clients.html | 2 +-
docs/2.0/getting-started/design.html | 2 +-
docs/2.0/getting-started/quick-install.html | 2 +-
docs/2.0/getting-started/shell.html | 2 +-
docs/2.0/getting-started/table_configuration.html | 6 +-
docs/2.0/getting-started/table_design.html | 2 +-
docs/2.0/troubleshooting/advanced.html | 2 +-
docs/2.0/troubleshooting/basic.html | 2 +-
.../troubleshooting/system-metadata-tables.html | 2 +-
docs/2.0/troubleshooting/tools.html | 2 +-
feed.xml | 4 +-
33 files changed, 393 insertions(+), 394 deletions(-)
diff --git a/contributor/making-release.html b/contributor/making-release.html
index 22f2a29..f852348 100644
--- a/contributor/making-release.html
+++ b/contributor/making-release.html
@@ -280,9 +280,9 @@ for two markdown files that should be changed in the Accumulo repo and copied/mi
</div>
</li>
<li>
- <p><code class="highlighter-rouge">configuration-properties</code> is copied after it is generated by the Accumulo build.</p>
+ <p><code class="highlighter-rouge">properties.md</code> is copied after it is generated by the Accumulo build.</p>
- <div class="highlighter-rouge"><pre class="highlight"><code> cp /path/to/accumulo/core/target/generated-docs/configuration-properties.md /path/to/accumulo-website/_docs-2-x/administration/configuration-properties.md
+ <div class="highlighter-rouge"><pre class="highlight"><code> cp /path/to/accumulo/core/target/generated-docs/properties.md /path/to/accumulo-website/_docs-2-x/administration/properties.md
</code></pre>
</div>
</li>
@@ -312,13 +312,13 @@ the directory name:</p>
releases.</p>
</li>
<li>
- <p>Copy <code class="highlighter-rouge">configuration-properties</code> and mirror <code class="highlighter-rouge">INSTALL.md</code>.</p>
+ <p>Copy <code class="highlighter-rouge">properties.md</code> and mirror <code class="highlighter-rouge">INSTALL.md</code>.</p>
</li>
</ol>
<p>Once a collection is created for a 2.x minor release, developers can make documentation updates like normal website updates.</p>
-<p><strong>For 2.x bugfix releases,</strong> copy <code class="highlighter-rouge">configuration-properties</code> and mirror <code class="highlighter-rouge">INSTALL.md</code>.</p>
+<p><strong>For 2.x bugfix releases,</strong> copy <code class="highlighter-rouge">properties.md</code> and mirror <code class="highlighter-rouge">INSTALL.md</code>.</p>
<p><strong>For 1.x minor & bugfix releases,</strong> copy <code class="highlighter-rouge">accumulo_user_manual.html</code> generated for release to the <code class="highlighter-rouge">1.x/</code> directory in the <a href="https://github.com/apache/accumulo-website">accumulo-website repo</a>.</p>
diff --git a/css/accumulo.css b/css/accumulo.css
index d3c283a..40a6d68 100644
--- a/css/accumulo.css
+++ b/css/accumulo.css
@@ -264,6 +264,9 @@ h2:hover .header-link, h3:hover .header-link, h4:hover .header-link, h5:hover .h
/* insert invisible space above header elements with an id attribute, so that if they are linked to, the actual content will appear below the nav menu */
h1[id]::before, h2[id]::before, h3[id]::before, h4[id]::before, h5[id]::before, h6[id]::before { display: block; content: " "; margin-top: -80px; height: 80px; visibility: hidden; }
+/* insert invisible space above Accumulo property names so that if they are linked to, the actual content will appear below the nav menu */
+a.prop { display: block; content: " "; margin-top: -90px; height: 90px; visibility: hidden; }
+
/* Turn off sidebar affix for small screens */
@media (max-width: 975px) { .affix { position: static; } }
/* Makes navbar collapse at larger width (1050px) */
diff --git a/docs/2.0/administration/caching.html b/docs/2.0/administration/caching.html
index 1b5ba68..222e31c 100644
--- a/docs/2.0/administration/caching.html
+++ b/docs/2.0/administration/caching.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
@@ -351,8 +351,8 @@ for tables where read performance is critical.</p>
for all other tables by setting the following table properties to <code class="highlighter-rouge">true</code>:</p>
<ul>
- <li><a href="/docs/2.0/administration/configuration-properties#table_cache_block_enable">table.cache.block.enable</a> - enables data block cache on the table</li>
- <li><a href="/docs/2.0/administration/configuration-properties#table_cache_index_enable">table.cache.index.enable</a> - enables index block cache on the table</li>
+ <li><a href="/docs/2.0/administration/properties#table_cache_block_enable">table.cache.block.enable</a> - enables data block cache on the table</li>
+ <li><a href="/docs/2.0/administration/properties#table_cache_index_enable">table.cache.index.enable</a> - enables index block cache on the table</li>
</ul>
<p>These properties can be set in the Accumulo shell using the following command:</p>
@@ -371,8 +371,8 @@ for all other tables by setting the following table properties to <code class="h
the following properties:</p>
<ul>
- <li><a href="/docs/2.0/administration/configuration-properties#tserver_cache_data_size">tserver.cache.data.size</a></li>
- <li><a href="/docs/2.0/administration/configuration-properties#tserver_cache_data_size">tserver.cache.index.size</a></li>
+ <li><a href="/docs/2.0/administration/properties#tserver_cache_data_size">tserver.cache.data.size</a></li>
+ <li><a href="/docs/2.0/administration/properties#tserver_cache_data_size">tserver.cache.index.size</a></li>
</ul>
diff --git a/docs/2.0/administration/configuration-management.html b/docs/2.0/administration/configuration-management.html
index 073a9f4..ae7cdbf 100644
--- a/docs/2.0/administration/configuration-management.html
+++ b/docs/2.0/administration/configuration-management.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
@@ -334,7 +334,7 @@
<h2 id="setting-configuration">Setting Configuration</h2>
-<p>Accumulo is configured using <a href="/docs/2.0/administration/configuration-properties">properties</a> whose values can be set in the following locations (with increasing precedence):</p>
+<p>Accumulo is configured using <a href="/docs/2.0/administration/properties">properties</a> whose values can be set in the following locations (with increasing precedence):</p>
<ol>
<li>Default values</li>
@@ -348,26 +348,26 @@
<h3 id="default-values">Default values</h3>
-<p>All <a href="/docs/2.0/administration/configuration-properties">properties</a> have a default value that is listed for each property on the <a href="/docs/2.0/administration/configuration-properties">properties</a> page. Default values are set in the source code.
+<p>All <a href="/docs/2.0/administration/properties">properties</a> have a default value that is listed for each property on the <a href="/docs/2.0/administration/properties">properties</a> page. Default values are set in the source code.
While default values have the lowest precedence, they are usually optimal. However, there are cases where a change can increase query and ingest performance.</p>
<h3 id="accumulo-sitexml">accumulo-site.xml</h3>
-<p>Setting <a href="/docs/2.0/administration/configuration-properties">properties</a> in accumulo-site.xml will override their default value. If you are running Accumulo on a cluster, any updates to accumulo-site.xml must
+<p>Setting <a href="/docs/2.0/administration/properties">properties</a> in accumulo-site.xml will override their default value. If you are running Accumulo on a cluster, any updates to accumulo-site.xml must
be synced across the cluster. Accumulo processes (master, tserver, etc) read their local accumulo-site.xml on start up so processes must be restarted to apply changes.
Certain properties can only be set in accumulo-site.xml. These properties have <strong>zk mutable: no</strong> in their description. Setting properties in accumulo-site.xml allows you
to configure tablet servers with different settings.</p>
<h3 id="zookeeper">Zookeeper</h3>
-<p>Many <a href="/docs/2.0/administration/configuration-properties">properties</a> can be set in Zookeeper using the Accumulo API or shell. These properties can identified by <strong>zk mutable: yes</strong> in their description on
-the <a href="/docs/2.0/administration/configuration-properties">properties page</a>. Zookeeper properties can be applied on a per-table or system-wide basis. Per-table properties take precedence over system-wide
+<p>Many <a href="/docs/2.0/administration/properties">properties</a> can be set in Zookeeper using the Accumulo API or shell. These properties can identified by <strong>zk mutable: yes</strong> in their description on
+the <a href="/docs/2.0/administration/properties">properties page</a>. Zookeeper properties can be applied on a per-table or system-wide basis. Per-table properties take precedence over system-wide
properties. While most properties set in Zookeeper take effect immediately, some require a restart of the process which is indicated in <strong>zk mutable</strong> section
of their description.</p>
<h4 id="zookeeper-system-properties">Zookeeper System properties</h4>
-<p>System properties consist of all <a href="/docs/2.0/administration/configuration-properties">properties</a> with <strong>zk mutable: yes</strong> in their description. They are set with the following shell command:</p>
+<p>System properties consist of all <a href="/docs/2.0/administration/properties">properties</a> with <strong>zk mutable: yes</strong> in their description. They are set with the following shell command:</p>
<div class="highlighter-rouge"><pre class="highlight"><code>config -s PROPERTY=VALUE
</code></pre>
@@ -377,7 +377,7 @@ of their description.</p>
<h4 id="zookeeper-table-properties">Zookeeper Table properties</h4>
-<p><a href="/docs/2.0/administration/configuration-properties#table_prefix">Table properties</a> consist of all properties with the <code class="highlighter-rouge">table.*</code> prefix.</p>
+<p><a href="/docs/2.0/administration/properties#table_prefix">Table properties</a> consist of all properties with the <code class="highlighter-rouge">table.*</code> prefix.</p>
<p>Table properties are configured for a table namespace (i.e group of tables) or on a per-table basis.</p>
@@ -397,7 +397,7 @@ of their description.</p>
<h4 id="zookeeper-considerations">Zookeeper Considerations</h4>
-<p>Any <a href="/docs/2.0/administration/configuration-properties">properties</a> that are set in Zookeeper should consider the limitations of Zookeeper itself with respect to the
+<p>Any <a href="/docs/2.0/administration/properties">properties</a> that are set in Zookeeper should consider the limitations of Zookeeper itself with respect to the
number of nodes and the size of the node data. Custom table properties and options for Iterators configured on tables
are two areas in which there aren’t any fail safes built into the API that can prevent the user from making this mistake.</p>
diff --git a/docs/2.0/administration/fate.html b/docs/2.0/administration/fate.html
index deda762..bcf6ed2 100644
--- a/docs/2.0/administration/fate.html
+++ b/docs/2.0/administration/fate.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/administration/in-depth-install.html b/docs/2.0/administration/in-depth-install.html
index b5c6b3e..7775183 100644
--- a/docs/2.0/administration/in-depth-install.html
+++ b/docs/2.0/administration/in-depth-install.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
@@ -379,32 +379,32 @@ their value in accumulo-site.xml.</p>
<tr>
<td>4560</td>
<td>Accumulo monitor (for centralized log display)</td>
- <td>monitor.port.log4j</td>
+ <td><a href="/docs/2.0/administration/properties#monitor_port_log4j">monitor.port.log4j</a></td>
</tr>
<tr>
<td>9995</td>
<td>Accumulo HTTP monitor</td>
- <td>monitor.port.client</td>
+ <td><a href="/docs/2.0/administration/properties#monitor_port_client">monitor.port.client</a></td>
</tr>
<tr>
<td>9997</td>
<td>Tablet Server</td>
- <td>tserver.port.client</td>
+ <td><a href="/docs/2.0/administration/properties#tserver_port_client">tserver.port.client</a></td>
</tr>
<tr>
<td>9998</td>
<td>Accumulo GC</td>
- <td>gc.port.client</td>
+ <td><a href="/docs/2.0/administration/properties#gc_port_client">gc.port.client</a></td>
</tr>
<tr>
<td>9999</td>
<td>Master Server</td>
- <td>master.port.client</td>
+ <td><a href="/docs/2.0/administration/properties#master_port_client">master.port.client</a></td>
</tr>
<tr>
<td>12234</td>
<td>Accumulo Tracer</td>
- <td>trace.port.client</td>
+ <td><a href="/docs/2.0/administration/properties#trace_port_client">trace.port.client</a></td>
</tr>
<tr>
<td>42424</td>
@@ -414,12 +414,12 @@ their value in accumulo-site.xml.</p>
<tr>
<td>10001</td>
<td>Master Replication service</td>
- <td>master.replication.coordinator.port</td>
+ <td><a href="/docs/2.0/administration/properties#master_replication_coordinator_port">master.replication.coordinator.port</a></td>
</tr>
<tr>
<td>10002</td>
<td>TabletServer Replication service</td>
- <td>replication.receipt.service.port</td>
+ <td><a href="/docs/2.0/administration/properties#replication_receipt_service_port">replication.receipt.service.port</a></td>
</tr>
</tbody>
</table>
@@ -554,30 +554,34 @@ also locate the native maps shared library by setting <code class="highlighter-r
<h4 id="native-maps-configuration">Native Maps Configuration</h4>
<p>As mentioned, Accumulo will use the native libraries if they are found in the expected
-location and <code class="highlighter-rouge">tserver.memory.maps.native.enabled</code> is set to <code class="highlighter-rouge">true</code> (which is the default).
+location and <a href="/docs/2.0/administration/properties#tserver_memory_maps_native_enabled">tserver.memory.maps.native.enabled</a> is set to <code class="highlighter-rouge">true</code> (which is the default).
Using the native maps over JVM Maps nets a noticeable improvement in ingest rates; however,
certain configuration variables are important to modify when increasing the size of the
native map.</p>
-<p>To adjust the size of the native map, increase the value of <code class="highlighter-rouge">tserver.memory.maps.max</code>.
-By default, the maximum size of the native map is 1GB. When increasing this value, it is
-also important to adjust the values of <code class="highlighter-rouge">table.compaction.minor.logs.threshold</code> and
-<code class="highlighter-rouge">tserver.walog.max.size</code>. <code class="highlighter-rouge">table.compaction.minor.logs.threshold</code> is the maximum
-number of write-ahead log files that a tablet can reference before they will be automatically
-minor compacted. <code class="highlighter-rouge">tserver.walog.max.size</code> is the maximum size of a write-ahead log.</p>
+<p>To adjust the size of the native map, modify the value of <a href="/docs/2.0/administration/properties#tserver_memory_maps_max">tserver.memory.maps.max</a>. When increasing
+this value, it is also important to adjust the values below:</p>
-<p>The maximum size of the native maps for a server should be less than the product
-of the write-ahead log maximum size and minor compaction threshold for log files:</p>
+<ul>
+ <li><a href="/docs/2.0/administration/properties#table_compaction_minor_logs_threshold">table.compaction.minor.logs.threshold</a> - maximum number of write-ahead log files that a tablet can
+reference before they will be automatically minor compacted</li>
+ <li><a href="/docs/2.0/administration/properties#tserver_walog_max_size">tserver.walog.max.size</a> - maximum size of a write-ahead log.</li>
+</ul>
+
+<p>The maximum size of the native maps for a server should be less than the product of the write-ahead
+log maximum size and minor compaction threshold for log files:</p>
-<p><code class="highlighter-rouge">$table.compaction.minor.logs.threshold * $tserver.walog.max.size >= $tserver.memory.maps.max</code></p>
+<div class="highlighter-rouge"><pre class="highlight"><code>$table.compaction.minor.logs.threshold * $tserver.walog.max.size >= $tserver.memory.maps.max
+</code></pre>
+</div>
<p>This formula ensures that minor compactions won’t be automatically triggered before the native
maps can be completely saturated.</p>
<p>Subsequently, when increasing the size of the write-ahead logs, it can also be important
to increase the HDFS block size that Accumulo uses when creating the files for the write-ahead log.
-This is controlled via <code class="highlighter-rouge">tserver.wal.blocksize</code>. A basic recommendation is that when
-<code class="highlighter-rouge">tserver.walog.max.size</code> is larger than 2GB in size, set <code class="highlighter-rouge">tserver.wal.blocksize</code> to 2GB.
+This is controlled via <a href="/docs/2.0/administration/properties#tserver_wal_blocksize">tserver.wal.blocksize</a>. A basic recommendation is that when
+<a href="/docs/2.0/administration/properties#tserver_walog_max_size">tserver.walog.max.size</a> is larger than 2GB in size, set <a href="/docs/2.0/administration/properties#tserver_wal_blocksize">tserver.wal.blocksize</a> to 2GB.
Increasing the block size to a value larger than 2GB can result in decreased write
performance to the write-ahead log file which will slow ingest.</p>
@@ -597,30 +601,16 @@ of errors.</p>
<h3 id="configure-accumulo-sitexml">Configure accumulo-site.xml</h3>
-<p>Specify appropriate values for the following settings in <code class="highlighter-rouge">accumulo-site.xml</code>:</p>
-
-<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><property></span>
- <span class="nt"><name></span>instance.zookeeper.host<span class="nt"></name></span>
- <span class="nt"><value></span>zooserver-one:2181,zooserver-two:2181<span class="nt"></value></span>
- <span class="nt"><description></span>list of zookeeper servers<span class="nt"></description></span>
-<span class="nt"></property></span>
-</code></pre>
-</div>
-
-<p>This enables Accumulo to find ZooKeeper. Accumulo uses ZooKeeper to coordinate
-settings between processes and helps finalize TabletServer failure.</p>
+<p>Specify appropriate values for the following properties in <code class="highlighter-rouge">accumulo-site.xml</code>:</p>
-<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><property></span>
- <span class="nt"><name></span>instance.secret<span class="nt"></name></span>
- <span class="nt"><value></span>DEFAULT<span class="nt"></value></span>
-<span class="nt"></property></span>
-</code></pre>
-</div>
-
-<p>The instance needs a secret to enable secure communication between servers. Configure your
-secret and make sure that the <code class="highlighter-rouge">accumulo-site.xml</code> file is not readable to other users.
-For alternatives to storing the <code class="highlighter-rouge">instance.secret</code> in plaintext, please read the
-<code class="highlighter-rouge">Sensitive Configuration Values</code> section.</p>
+<ul>
+ <li><a href="/docs/2.0/administration/properties#instance_zookeeper_host">instance.zookeeper.host</a> - Enables Accumulo to find ZooKeeper. Accumulo uses ZooKeeper
+to coordinate settings between processes and helps finalize TabletServer failure.</li>
+ <li><a href="/docs/2.0/administration/properties#instance_secret">instance.secret</a> - The instance needs a secret to enable secure communication between servers.
+Configure your secret and make sure that the <code class="highlighter-rouge">accumulo-site.xml</code> file is not readable to other users.
+For alternatives to storing the <a href="/docs/2.0/administration/properties#instance_secret">instance.secret</a> in plaintext, please read the
+<a href="#sensitive-configuration-values">Sensitive Configuration Values</a> section.</li>
+</ul>
<p>Some settings can be modified via the Accumulo shell and take effect immediately, but
some settings require a process restart to take effect. See the <a href="/docs/2.0/administration/configuration-management">configuration management</a>
@@ -652,7 +642,7 @@ where that command is run.</p>
<h3 id="sensitive-configuration-values">Sensitive Configuration Values</h3>
<p>Accumulo has a number of properties that can be specified via the accumulo-site.xml
-file which are sensitive in nature, instance.secret and trace.token.property.password
+file which are sensitive in nature, <a href="/docs/2.0/administration/properties#instance_secret">instance.secret</a> and <code class="highlighter-rouge">trace.token.property.password</code>
are two common examples. Both of these properties, if compromised, have the ability
to result in data being leaked to users who should not have access to that data.</p>
@@ -663,14 +653,14 @@ is a candidate for use with these CredentialProviders. For version of Hadoop whi
these classes, the feature will just be unavailable for use.</p>
<p>A comma separated list of CredentialProviders can be configured using the Accumulo Property
-<code class="highlighter-rouge">general.security.credential.provider.paths</code>. Each configured URL will be consulted
+<a href="/docs/2.0/administration/properties#general_security_credential_provider_paths">general.security.credential.provider.paths</a>. Each configured URL will be consulted
when the Configuration object for accumulo-site.xml is accessed.</p>
<h3 id="using-a-javakeystorecredentialprovider-for-storage">Using a JavaKeyStoreCredentialProvider for storage</h3>
<p>One of the implementations provided in Hadoop-2.6.0 is a Java KeyStore CredentialProvider.
Each entry in the KeyStore is the Accumulo Property key name. For example, to store the
-<code class="highlighter-rouge">instance.secret</code>, the following command can be used:</p>
+<a href="/docs/2.0/administration/properties#instance_secret">instance.secret</a>, the following command can be used:</p>
<div class="highlighter-rouge"><pre class="highlight"><code>hadoop credential create instance.secret --provider jceks://file/etc/accumulo/conf/accumulo.jceks
</code></pre>
@@ -691,7 +681,7 @@ Each entry in the KeyStore is the Accumulo Property key name. For example, to st
</code></pre>
</div>
-<p>This configuration will then transparently extract the <code class="highlighter-rouge">instance.secret</code> from
+<p>This configuration will then transparently extract the <a href="/docs/2.0/administration/properties#instance_secret">instance.secret</a> from
the configured KeyStore and alleviates a human readable storage of the sensitive
property.</p>
@@ -740,14 +730,14 @@ consideration. There is no enforcement of these warnings via the API.</p>
<h4 id="configuring-the-classloader">Configuring the ClassLoader</h4>
<p>Accumulo builds its Java classpath in <code class="highlighter-rouge">accumulo-env.sh</code>. After an Accumulo application has started, it will load classes from the locations
-specified in the deprecated <code class="highlighter-rouge">general.classpaths</code> property. Additionally, Accumulo will load classes from the locations specified in the
-<code class="highlighter-rouge">general.dynamic.classpaths</code> property and will monitor and reload them if they change. The reloading feature is useful during the development
+specified in the deprecated <a href="/docs/2.0/administration/properties#general_classpaths">general.classpaths</a> property. Additionally, Accumulo will load classes from the locations specified in the
+<a href="/docs/2.0/administration/properties#general_dynamic_classpaths">general.dynamic.classpaths</a> property and will monitor and reload them if they change. The reloading feature is useful during the development
and testing of iterators as new or modified iterator classes can be deployed to Accumulo without having to restart the database.
/
Accumulo also has an alternate configuration for the classloader which will allow it to load classes from remote locations. This mechanism
uses Apache Commons VFS which enables locations such as http and hdfs to be used. This alternate configuration also uses the
-<code class="highlighter-rouge">general.classpaths</code> property in the same manner described above. It differs in that you need to configure the
-<code class="highlighter-rouge">general.vfs.classpaths</code> property instead of the <code class="highlighter-rouge">general.dynamic.classpath</code> property. As in the default configuration, this alternate
+<a href="/docs/2.0/administration/properties#general_classpaths">general.classpaths</a> property in the same manner described above. It differs in that you need to configure the
+<a href="/docs/2.0/administration/properties#general_vfs_classpaths">general.vfs.classpaths</a> property instead of the <a href="/docs/2.0/administration/properties#general_dynamic_classpaths">general.dynamic.classpaths</a> property. As in the default configuration, this alternate
configuration will also monitor the vfs locations for changes and reload if necessary.</p>
<p>The Accumulo classpath can be viewed in human readable format by running <code class="highlighter-rouge">accumulo classpath -d</code>.</p>
diff --git a/docs/2.0/administration/kerberos.html b/docs/2.0/administration/kerberos.html
index 3a09379..0b9c2d0 100644
--- a/docs/2.0/administration/kerberos.html
+++ b/docs/2.0/administration/kerberos.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/administration/monitoring-metrics.html b/docs/2.0/administration/monitoring-metrics.html
index 9bb490b..3ab8666 100644
--- a/docs/2.0/administration/monitoring-metrics.html
+++ b/docs/2.0/administration/monitoring-metrics.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
@@ -371,12 +371,12 @@ is strongly recommended that the Monitor is not exposed to any publicly-accessib
<p>SSL may be enabled for the monitor page by setting the following properties in the <code class="highlighter-rouge">accumulo-site.xml</code> file:</p>
-<div class="highlighter-rouge"><pre class="highlight"><code>monitor.ssl.keyStore
-monitor.ssl.keyStorePassword
-monitor.ssl.trustStore
-monitor.ssl.trustStorePassword
-</code></pre>
-</div>
+<ul>
+ <li><a href="/docs/2.0/administration/properties#monitor_ssl_keyStore">monitor.ssl.keyStore</a></li>
+ <li><a href="/docs/2.0/administration/properties#monitor_ssl_keystorePassword">monitor.ssl.keyStorePassword</a></li>
+ <li><a href="/docs/2.0/administration/properties#monitor_ssl_trustStore">monitor.ssl.trustStore</a></li>
+ <li><a href="/docs/2.0/administration/properties#monitor_ssl_trustStorePassword">monitor.ssl.trustStorePassword</a></li>
+</ul>
<p>If the Accumulo conf directory has been configured (in particular the <code class="highlighter-rouge">accumulo-env.sh</code> file must be set up), the
<code class="highlighter-rouge">accumulo-util gen-monitor-cert</code> command can be used to create the keystore and truststore files with random passwords. The command
@@ -385,10 +385,10 @@ Java <code class="highlighter-rouge">keytool</code> command, whose usage can be
<p>If desired, the SSL ciphers allowed for connections can be controlled via the following properties in <code class="highlighter-rouge">accumulo-site.xml</code>:</p>
-<div class="highlighter-rouge"><pre class="highlight"><code>monitor.ssl.include.ciphers
-monitor.ssl.exclude.ciphers
-</code></pre>
-</div>
+<ul>
+ <li><a href="/docs/2.0/administration/properties#monitor_ssl_include_ciphers">monitor.ssl.include.ciphers</a></li>
+ <li><a href="/docs/2.0/administration/properties#monitor_ssl_exclude_ciphers">monitor.ssl.exclude.ciphers</a></li>
+</ul>
<p>If SSL is enabled, the monitor URL can only be accessed via https.
This also allows you to access the Accumulo shell through the monitor page.
@@ -402,7 +402,7 @@ An Accumulo user name and password must be entered for access to the shell.</p>
<h3 id="legacy-metrics">Legacy Metrics</h3>
<p>Accumulo has a legacy metrics library that can be exposes metrics using JMX endpoints or file-based logging. These metrics can
-be enabled by setting <code class="highlighter-rouge">general.legacy.metrics</code> to <code class="highlighter-rouge">true</code> in <code class="highlighter-rouge">accumulo-site.xml</code> and placing the <code class="highlighter-rouge">accumulo-metrics.xml</code>
+be enabled by setting <a href="/docs/2.0/administration/properties#general_legacy_metrics">general.legacy.metrics</a> to <code class="highlighter-rouge">true</code> in <code class="highlighter-rouge">accumulo-site.xml</code> and placing the <code class="highlighter-rouge">accumulo-metrics.xml</code>
configuration file on the classpath (which is typically done by placing the file in the <code class="highlighter-rouge">conf/</code> directory). A template for
<code class="highlighter-rouge">accumulo-metrics.xml</code> can be found in <code class="highlighter-rouge">conf/templates</code> of the Accumulo tarball.</p>
diff --git a/docs/2.0/administration/multivolume.html b/docs/2.0/administration/multivolume.html
index 10446ac..70e5f81 100644
--- a/docs/2.0/administration/multivolume.html
+++ b/docs/2.0/administration/multivolume.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
@@ -338,7 +338,7 @@ under a lot of write pressure.</p>
<p>The HDFS NameNode holds all of the metadata about the files in
HDFS. For fast performance, all of this information needs to be stored
in memory. A single NameNode with 64G of memory can store the
-metadata for tens of millions of files.However, when scaling beyond a
+metadata for tens of millions of files. However, when scaling beyond a
thousand nodes, an active Accumulo system can generate lots of updates
to the file system, especially when data is being ingested. The large
number of write transactions to the NameNode, and the speed of a
@@ -352,7 +352,7 @@ routinely runs in less than a minute, the NameNode is performing well.</p>
<p>However, if you do begin to experience slow-down and poor GC
performance, Accumulo can be configured to use multiple NameNode
-servers. The configuration <code class="highlighter-rouge">instance.volumes</code> should be set to a
+servers. The configuration <a href="/docs/2.0/administration/properties#instance_volumes">instance.volumes</a> should be set to a
comma-separated list, using full URI references to different NameNode
servers:</p>
@@ -374,10 +374,10 @@ the same way they were before 1.6.</p>
moved to host2), then Accumulo will no longer function. Even if Hadoop and
Accumulo configurations are changed, the fully qualified URIs stored in
Accumulo will still contain the old URI. To handle this Accumulo has the
-following configuration property for replacing URI stored in its metadata. The
-example configuration below will replace ns1 with nsA and ns2 with nsB in
-Accumulo metadata. For this property to take affect, Accumulo will need to be
-restarted.</p>
+configuration property <a href="/docs/2.0/administration/properties#instance_volumes_replacements">instance.volumes.replacements</a> for replacing URI stored
+in its metadata. The example configuration below will replace ns1 with nsA and
+ns2 with nsB in Accumulo metadata. For this property to take affect, Accumulo will
+need to be restarted.</p>
<div class="language-xml highlighter-rouge"><pre class="highlight"><code><span class="nt"><property></span>
<span class="nt"><name></span>instance.volumes.replacements<span class="nt"></name></span>
@@ -401,6 +401,7 @@ NameNode servers, so you do not have to partition your DataNodes by
NameNode.</p>
+
<div class="row" style="margin-top: 20px;">
<div class="col-md-10"><strong>Find documentation for all releases in the <a href="/docs-archive">archive</strong></div>
<div class="col-md-2"><a class="pull-right" href="https://github.com/apache/accumulo-website/edit/master/_docs-2-0/administration/multivolume.md" role="button"><i class="glyphicon glyphicon-pencil"></i> <small>Edit this page</small></a></div>
diff --git a/docs/2.0/administration/configuration-properties.html b/docs/2.0/administration/properties.html
similarity index 77%
rename from docs/2.0/administration/configuration-properties.html
rename to docs/2.0/administration/properties.html
index f85b661..af7e62a 100644
--- a/docs/2.0/administration/configuration-properties.html
+++ b/docs/2.0/administration/properties.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
@@ -329,7 +329,7 @@
<div class="row">
<div class="col-md-10"><h1>Configuration Properties</h1></div>
- <div class="col-md-2"><a class="pull-right" style="margin-top: 25px;" href="https://github.com/apache/accumulo-website/edit/master/_docs-2-0/administration/configuration-properties.md" role="button"><i class="glyphicon glyphicon-pencil"></i> <small>Edit this page</small></a></div>
+ <div class="col-md-2"><a class="pull-right" style="margin-top: 25px;" href="https://github.com/apache/accumulo-website/edit/master/_docs-2-0/administration/properties.md" role="button"><i class="glyphicon glyphicon-pencil"></i> <small>Edit this page</small></a></div>
</div>
<!-- WARNING: Do not edit this file. It is a generated file that is copied from Accumulo build (from core/target/generated-docs) -->
@@ -343,943 +343,951 @@
</thead>
<tbody>
<tr>
- <td><a name="gc_prefix"></a> <strong>gc.</strong>*</td>
+ <td><a name="gc_prefix" class="prop"></a> <strong>gc.</strong>*</td>
<td>Properties in this category affect the behavior of the accumulo garbage collector.</td>
</tr>
<tr>
- <td><a name="gc_cycle_delay"></a> gc.cycle.delay</td>
+ <td><a name="gc_cycle_delay" class="prop"></a> gc.cycle.delay</td>
<td>Time between garbage collection cycles. In each cycle, old files no longer in use are removed from the filesystem.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5m</code></td>
</tr>
<tr>
- <td><a name="gc_cycle_start"></a> gc.cycle.start</td>
+ <td><a name="gc_cycle_start" class="prop"></a> gc.cycle.start</td>
<td>Time to wait before attempting to garbage collect any old files.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">30s</code></td>
</tr>
<tr>
- <td><a name="gc_file_archive"></a> gc.file.archive</td>
+ <td><a name="gc_file_archive" class="prop"></a> gc.file.archive</td>
<td>Archive any files/directories instead of moving to the HDFS trash or deleting.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="gc_port_client"></a> gc.port.client</td>
+ <td><a name="gc_port_client" class="prop"></a> gc.port.client</td>
<td>The listening port for the garbage collector’s monitor service<br /><strong>type:</strong> PORT, <strong>zk mutable:</strong> yes but requires restart of the gc, <strong>default value:</strong> <code class="highlighter-rouge">9998</code></td>
</tr>
<tr>
- <td><a name="gc_threads_delete"></a> gc.threads.delete</td>
+ <td><a name="gc_threads_delete" class="prop"></a> gc.threads.delete</td>
<td>The number of threads used to delete files<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">16</code></td>
</tr>
<tr>
- <td><a name="gc_trace_percent"></a> gc.trace.percent</td>
+ <td><a name="gc_trace_percent" class="prop"></a> gc.trace.percent</td>
<td>Percent of gc cycles to trace<br /><strong>type:</strong> FRACTION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0.01</code></td>
</tr>
<tr>
- <td><a name="gc_trash_ignore"></a> gc.trash.ignore</td>
+ <td><a name="gc_trash_ignore" class="prop"></a> gc.trash.ignore</td>
<td>Do not use the Trash, even if it is configured.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="general_prefix"></a> <strong>general.</strong>*</td>
+ <td><a name="general_prefix" class="prop"></a> <strong>general.</strong>*</td>
<td>Properties in this category affect the behavior of accumulo overall, but do not have to be consistent throughout a cloud.</td>
</tr>
<tr>
- <td><a name="general_classpaths"></a> general.classpaths</td>
+ <td><a name="general_classpaths" class="prop"></a> general.classpaths</td>
<td><strong>Deprecated.</strong> <del>This property is deprecated. The class path should instead be configured by the launch environment (for example, accumulo-env.sh). A list of all of the places to look for a class. Order does matter, as it will look for the jar starting in the first location to the last. Supports full regex on filename alone.</del><br /><del><strong>type:</strong> STRING</del>, <del><strong>zk mutable:</strong> no</del>, <del><strong>default value:</strong> empt [...]
</tr>
<tr>
- <td><a name="general_custom_prefix"></a> <strong>general.custom.</strong>*</td>
+ <td><a name="general_custom_prefix" class="prop"></a> <strong>general.custom.</strong>*</td>
<td>Prefix to be used for user defined system-wide properties. This may be particularly useful for system-wide configuration for various user-implementations of pluggable Accumulo features, such as the balancer or volume chooser.</td>
</tr>
<tr>
- <td><a name="general_delegation_token_lifetime"></a> general.delegation.token.lifetime</td>
+ <td><a name="general_delegation_token_lifetime" class="prop"></a> general.delegation.token.lifetime</td>
<td>The length of time that delegation tokens and secret keys are valid<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">7d</code></td>
</tr>
<tr>
- <td><a name="general_delegation_token_update_interval"></a> general.delegation.token.update.interval</td>
+ <td><a name="general_delegation_token_update_interval" class="prop"></a> general.delegation.token.update.interval</td>
<td>The length of time between generation of new secret keys<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">1d</code></td>
</tr>
<tr>
- <td><a name="general_dynamic_classpaths"></a> general.dynamic.classpaths</td>
+ <td><a name="general_dynamic_classpaths" class="prop"></a> general.dynamic.classpaths</td>
<td>A list of all of the places where changes in jars or classes will force a reload of the classloader.<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">$ACCUMULO_HOME/lib/ext/[^.].*.jar</code></td>
</tr>
<tr>
- <td><a name="general_kerberos_keytab"></a> general.kerberos.keytab</td>
+ <td><a name="general_kerberos_keytab" class="prop"></a> general.kerberos.keytab</td>
<td>Path to the kerberos keytab to use. Leave blank if not using kerberoized hdfs<br /><strong>type:</strong> PATH, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="general_kerberos_principal"></a> general.kerberos.principal</td>
+ <td><a name="general_kerberos_principal" class="prop"></a> general.kerberos.principal</td>
<td>Name of the kerberos principal to use. _HOST will automatically be replaced by the machines hostname in the hostname portion of the principal. Leave blank if not using kerberoized hdfs<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="general_kerberos_renewal_period"></a> general.kerberos.renewal.period</td>
+ <td><a name="general_kerberos_renewal_period" class="prop"></a> general.kerberos.renewal.period</td>
<td>The amount of time between attempts to perform Kerberos ticket renewals. This does not equate to how often tickets are actually renewed (which is performed at 80% of the ticket lifetime).<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">30s</code></td>
</tr>
<tr>
- <td><a name="general_legacy_metrics"></a> general.legacy.metrics</td>
+ <td><a name="general_legacy_metrics" class="prop"></a> general.legacy.metrics</td>
<td>Use the old metric infrastructure configured by accumulo-metrics.xml, instead of Hadoop Metrics2<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="general_max_scanner_retry_period"></a> general.max.scanner.retry.period</td>
+ <td><a name="general_max_scanner_retry_period" class="prop"></a> general.max.scanner.retry.period</td>
<td>The maximum amount of time that a Scanner should wait before retrying a failed RPC<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">5s</code></td>
</tr>
<tr>
- <td><a name="general_rpc_timeout"></a> general.rpc.timeout</td>
+ <td><a name="general_rpc_timeout" class="prop"></a> general.rpc.timeout</td>
<td>Time to wait on I/O for simple, short RPC calls<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">120s</code></td>
</tr>
<tr>
- <td><a name="general_security_credential_provider_paths"></a> general.security.credential.provider.paths</td>
+ <td><a name="general_security_credential_provider_paths" class="prop"></a> general.security.credential.provider.paths</td>
<td>Comma-separated list of paths to CredentialProviders<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="general_server_message_size_max"></a> general.server.message.size.max</td>
+ <td><a name="general_server_message_size_max" class="prop"></a> general.server.message.size.max</td>
<td>The maximum size of a message that can be sent to a server.<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">1G</code></td>
</tr>
<tr>
- <td><a name="general_server_simpletimer_threadpool_size"></a> general.server.simpletimer.threadpool.size</td>
+ <td><a name="general_server_simpletimer_threadpool_size" class="prop"></a> general.server.simpletimer.threadpool.size</td>
<td>The number of threads to use for server-internal scheduled tasks<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">1</code></td>
</tr>
<tr>
- <td><a name="general_vfs_cache_dir"></a> general.vfs.cache.dir</td>
+ <td><a name="general_vfs_cache_dir" class="prop"></a> general.vfs.cache.dir</td>
<td>Directory to use for the vfs cache. The cache will keep a soft reference to all of the classes loaded in the VM. This should be on local disk on each node with sufficient space. It defaults to ${java.io.tmpdir}/accumulo-vfs-cache-${user.name}<br /><strong>type:</strong> ABSOLUTEPATH, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">${java.io.tmpdir}/accumulo-vfs-cache-${user.name}</code></td>
</tr>
<tr>
- <td><a name="general_vfs_classpaths"></a> general.vfs.classpaths</td>
+ <td><a name="general_vfs_classpaths" class="prop"></a> general.vfs.classpaths</td>
<td>Configuration for a system level vfs classloader. Accumulo jar can be configured here and loaded out of HDFS.<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="general_vfs_context_classpath_prefix"></a> <strong>general.vfs.context.classpath.</strong>*</td>
+ <td><a name="general_vfs_context_classpath_prefix" class="prop"></a> <strong>general.vfs.context.classpath.</strong>*</td>
<td>Properties in this category are define a classpath. These properties start with the category prefix, followed by a context name. The value is a comma seperated list of URIs. Supports full regex on filename alone. For example, general.vfs.context.classpath.cx1=hdfs://nn1:9902/mylibdir/*.jar. You can enable post delegation for a context, which will load classes from the context first instead of the parent first. Do this by setting general.vfs.context.classpath.<name>.delegation= [...]
</tr>
<tr>
- <td><a name="instance_prefix"></a> <strong>instance.</strong>*</td>
+ <td><a name="instance_prefix" class="prop"></a> <strong>instance.</strong>*</td>
<td>Properties in this category must be consistent throughout a cloud. This is enforced and servers won’t be able to communicate if these differ.</td>
</tr>
<tr>
- <td><a name="instance_dfs_dir"></a> instance.dfs.dir</td>
+ <td><a name="instance_dfs_dir" class="prop"></a> instance.dfs.dir</td>
<td><strong>Deprecated.</strong> <del>HDFS directory in which accumulo instance will run. Do not change after accumulo is initialized.</del><br /><del><strong>type:</strong> ABSOLUTEPATH</del>, <del><strong>zk mutable:</strong> no</del>, <del><strong>default value:</strong> <code class="highlighter-rouge">/accumulo</code></del></td>
</tr>
<tr>
- <td><a name="instance_dfs_uri"></a> instance.dfs.uri</td>
+ <td><a name="instance_dfs_uri" class="prop"></a> instance.dfs.uri</td>
<td><strong>Deprecated.</strong> <del>A url accumulo should use to connect to DFS. If this is empty, accumulo will obtain this information from the hadoop configuration. This property will only be used when creating new files if instance.volumes is empty. After an upgrade to 1.6.0 Accumulo will start using absolute paths to reference files. Files created before a 1.6.0 upgrade are referenced via relative paths. Relative paths will always be resolved using this config (if empty usin [...]
</tr>
<tr>
- <td><a name="instance_rpc_sasl_allowed_host_impersonation"></a> instance.rpc.sasl.allowed.host.impersonation</td>
+ <td><a name="instance_rpc_sasl_allowed_host_impersonation" class="prop"></a> instance.rpc.sasl.allowed.host.impersonation</td>
<td>One-line configuration property controlling the network locations (hostnames) that are allowed to impersonate other users<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="instance_rpc_sasl_allowed_user_impersonation"></a> instance.rpc.sasl.allowed.user.impersonation</td>
+ <td><a name="instance_rpc_sasl_allowed_user_impersonation" class="prop"></a> instance.rpc.sasl.allowed.user.impersonation</td>
<td>One-line configuration property controlling what users are allowed to impersonate other users<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="instance_rpc_sasl_enabled"></a> instance.rpc.sasl.enabled</td>
+ <td><a name="instance_rpc_sasl_enabled" class="prop"></a> instance.rpc.sasl.enabled</td>
<td>Configures Thrift RPCs to require SASL with GSSAPI which supports Kerberos authentication. Mutually exclusive with SSL RPC configuration.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="instance_rpc_sasl_impersonation_prefix"></a> <strong>instance.rpc.sasl.impersonation.</strong>*</td>
+ <td><a name="instance_rpc_sasl_impersonation_prefix" class="prop"></a> <strong>instance.rpc.sasl.impersonation.</strong>*</td>
<td><strong>Deprecated.</strong> <del>Prefix that allows configuration of users that are allowed to impersonate other users</del></td>
</tr>
<tr>
- <td><a name="instance_rpc_ssl_clientAuth"></a> instance.rpc.ssl.clientAuth</td>
+ <td><a name="instance_rpc_ssl_clientAuth" class="prop"></a> instance.rpc.ssl.clientAuth</td>
<td>Require clients to present certs signed by a trusted root<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="instance_rpc_ssl_enabled"></a> instance.rpc.ssl.enabled</td>
+ <td><a name="instance_rpc_ssl_enabled" class="prop"></a> instance.rpc.ssl.enabled</td>
<td>Use SSL for socket connections from clients and among accumulo services. Mutually exclusive with SASL RPC configuration.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="instance_secret"></a> instance.secret</td>
+ <td><a name="instance_secret" class="prop"></a> instance.secret</td>
<td>A secret unique to a given instance that all servers must know in order to communicate with one another.It should be changed prior to the initialization of Accumulo. To change it after Accumulo has been initialized, use the ChangeSecret tool and then update accumulo-site.xml everywhere. Before using the ChangeSecret tool, make sure Accumulo is not running and you are logged in as the user that controls Accumulo files in HDFS. To use the ChangeSecret tool, run the command: ./bi [...]
</tr>
<tr>
- <td><a name="instance_security_authenticator"></a> instance.security.authenticator</td>
+ <td><a name="instance_security_authenticator" class="prop"></a> instance.security.authenticator</td>
<td>The authenticator class that accumulo will use to determine if a user has privilege to perform an action<br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.server.security.handler.ZKAuthenticator</code></td>
</tr>
<tr>
- <td><a name="instance_security_authorizor"></a> instance.security.authorizor</td>
+ <td><a name="instance_security_authorizor" class="prop"></a> instance.security.authorizor</td>
<td>The authorizor class that accumulo will use to determine what labels a user has privilege to see<br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.server.security.handler.ZKAuthorizor</code></td>
</tr>
<tr>
- <td><a name="instance_security_permissionHandler"></a> instance.security.permissionHandler</td>
+ <td><a name="instance_security_permissionHandler" class="prop"></a> instance.security.permissionHandler</td>
<td>The permission handler class that accumulo will use to determine if a user has privilege to perform an action<br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.server.security.handler.ZKPermHandler</code></td>
</tr>
<tr>
- <td><a name="instance_volumes"></a> instance.volumes</td>
+ <td><a name="instance_volumes" class="prop"></a> instance.volumes</td>
<td>A comma seperated list of dfs uris to use. Files will be stored across these filesystems. If this is empty, then instance.dfs.uri will be used. After adding uris to this list, run ‘accumulo init –add-volume’ and then restart tservers. If entries are removed from this list then tservers will need to be restarted. After a uri is removed from the list Accumulo will not create new files in that location, however Accumulo can still reference files created at that location before the [...]
</tr>
<tr>
- <td><a name="instance_volumes_replacements"></a> instance.volumes.replacements</td>
+ <td><a name="instance_volumes_replacements" class="prop"></a> instance.volumes.replacements</td>
<td>Since accumulo stores absolute URIs changing the location of a namenode could prevent Accumulo from starting. The property helps deal with that situation. Provide a comma separated list of uri replacement pairs here if a namenode location changes. Each pair shold be separated with a space. For example, if hdfs://nn1 was replaced with hdfs://nnA and hdfs://nn2 was replaced with hdfs://nnB, then set this property to ‘hdfs://nn1 hdfs://nnA,hdfs://nn2 hdfs://nnB’ Replacements must [...]
</tr>
<tr>
- <td><a name="instance_zookeeper_host"></a> instance.zookeeper.host</td>
+ <td><a name="instance_zookeeper_host" class="prop"></a> instance.zookeeper.host</td>
<td>Comma separated list of zookeeper servers<br /><strong>type:</strong> HOSTLIST, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">localhost:2181</code></td>
</tr>
<tr>
- <td><a name="instance_zookeeper_timeout"></a> instance.zookeeper.timeout</td>
+ <td><a name="instance_zookeeper_timeout" class="prop"></a> instance.zookeeper.timeout</td>
<td>Zookeeper session timeout; max value when represented as milliseconds should be no larger than 2147483647<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">30s</code></td>
</tr>
<tr>
- <td><a name="master_prefix"></a> <strong>master.</strong>*</td>
+ <td><a name="master_prefix" class="prop"></a> <strong>master.</strong>*</td>
<td>Properties in this category affect the behavior of the master server</td>
</tr>
<tr>
- <td><a name="master_bulk_rename_threadpool_size"></a> master.bulk.rename.threadpool.size</td>
+ <td><a name="master_bulk_rename_threadpool_size" class="prop"></a> master.bulk.rename.threadpool.size</td>
<td>The number of threads to use when moving user files to bulk ingest directories under accumulo control<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">20</code></td>
</tr>
<tr>
- <td><a name="master_bulk_retries"></a> master.bulk.retries</td>
+ <td><a name="master_bulk_retries" class="prop"></a> master.bulk.retries</td>
<td>The number of attempts to bulk-load a file before giving up.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">3</code></td>
</tr>
<tr>
- <td><a name="master_bulk_threadpool_size"></a> master.bulk.threadpool.size</td>
+ <td><a name="master_bulk_threadpool_size" class="prop"></a> master.bulk.threadpool.size</td>
<td>The number of threads to use when coordinating a bulk-import.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5</code></td>
</tr>
<tr>
- <td><a name="master_bulk_timeout"></a> master.bulk.timeout</td>
+ <td><a name="master_bulk_timeout" class="prop"></a> master.bulk.timeout</td>
<td>The time to wait for a tablet server to process a bulk import request<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5m</code></td>
</tr>
<tr>
- <td><a name="master_fate_threadpool_size"></a> master.fate.threadpool.size</td>
+ <td><a name="master_bulk_tserver_regex" class="prop"></a> master.bulk.tserver.regex</td>
+ <td>Regular expression that defines the set of Tablet Servers that will perform bulk imports<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> empty</td>
+ </tr>
+ <tr>
+ <td><a name="master_fate_threadpool_size" class="prop"></a> master.fate.threadpool.size</td>
<td>The number of threads used to run FAult-Tolerant Executions. These are primarily table operations like merge.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">4</code></td>
</tr>
<tr>
- <td><a name="master_lease_recovery_interval"></a> master.lease.recovery.interval</td>
+ <td><a name="master_lease_recovery_interval" class="prop"></a> master.lease.recovery.interval</td>
<td>The amount of time to wait after requesting a WAL file to be recovered<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5s</code></td>
</tr>
<tr>
- <td><a name="master_metadata_suspendable"></a> master.metadata.suspendable</td>
+ <td><a name="master_metadata_suspendable" class="prop"></a> master.metadata.suspendable</td>
<td>Allow tablets for the accumulo.metadata table to be suspended via table.suspend.duration.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="master_port_client"></a> master.port.client</td>
+ <td><a name="master_port_client" class="prop"></a> master.port.client</td>
<td>The port used for handling client connections on the master<br /><strong>type:</strong> PORT, <strong>zk mutable:</strong> yes but requires restart of the master, <strong>default value:</strong> <code class="highlighter-rouge">9999</code></td>
</tr>
<tr>
- <td><a name="master_recovery_delay"></a> master.recovery.delay</td>
+ <td><a name="master_recovery_delay" class="prop"></a> master.recovery.delay</td>
<td>When a tablet server’s lock is deleted, it takes time for it to completely quit. This delay gives it time before log recoveries begin.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10s</code></td>
</tr>
<tr>
- <td><a name="master_recovery_max_age"></a> master.recovery.max.age</td>
+ <td><a name="master_recovery_max_age" class="prop"></a> master.recovery.max.age</td>
<td>Recovery files older than this age will be removed.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">60m</code></td>
</tr>
<tr>
- <td><a name="master_recovery_time_max"></a> master.recovery.time.max</td>
+ <td><a name="master_recovery_time_max" class="prop"></a> master.recovery.time.max</td>
<td>The maximum time to attempt recovery before giving up<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">30m</code></td>
</tr>
<tr>
- <td><a name="master_replication_coordinator_minthreads"></a> master.replication.coordinator.minthreads</td>
+ <td><a name="master_replication_coordinator_minthreads" class="prop"></a> master.replication.coordinator.minthreads</td>
<td>Minimum number of threads dedicated to answering coordinator requests<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">4</code></td>
</tr>
<tr>
- <td><a name="master_replication_coordinator_port"></a> master.replication.coordinator.port</td>
+ <td><a name="master_replication_coordinator_port" class="prop"></a> master.replication.coordinator.port</td>
<td>Port for the replication coordinator service<br /><strong>type:</strong> PORT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10001</code></td>
</tr>
<tr>
- <td><a name="master_replication_coordinator_threadcheck_time"></a> master.replication.coordinator.threadcheck.time</td>
+ <td><a name="master_replication_coordinator_threadcheck_time" class="prop"></a> master.replication.coordinator.threadcheck.time</td>
<td>The time between adjustments of the coordinator thread pool<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5s</code></td>
</tr>
<tr>
- <td><a name="master_replication_status_scan_interval"></a> master.replication.status.scan.interval</td>
+ <td><a name="master_replication_status_scan_interval" class="prop"></a> master.replication.status.scan.interval</td>
<td>Amount of time to sleep before scanning the status section of the replication table for new data<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">30s</code></td>
</tr>
<tr>
- <td><a name="master_server_threadcheck_time"></a> master.server.threadcheck.time</td>
+ <td><a name="master_server_threadcheck_time" class="prop"></a> master.server.threadcheck.time</td>
<td>The time between adjustments of the server thread pool.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1s</code></td>
</tr>
<tr>
- <td><a name="master_server_threads_minimum"></a> master.server.threads.minimum</td>
+ <td><a name="master_server_threads_minimum" class="prop"></a> master.server.threads.minimum</td>
<td>The minimum number of threads to use to handle incoming requests.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">20</code></td>
</tr>
<tr>
- <td><a name="master_status_threadpool_size"></a> master.status.threadpool.size</td>
+ <td><a name="master_status_threadpool_size" class="prop"></a> master.status.threadpool.size</td>
<td>The number of threads to use when fetching the tablet server status for balancing.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1</code></td>
</tr>
<tr>
- <td><a name="master_tablet_balancer"></a> master.tablet.balancer</td>
+ <td><a name="master_tablet_balancer" class="prop"></a> master.tablet.balancer</td>
<td>The balancer class that accumulo will use to make tablet assignment and migration decisions.<br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.server.master.balancer.TableLoadBalancer</code></td>
</tr>
<tr>
- <td><a name="master_walog_closer_implementation"></a> master.walog.closer.implementation</td>
+ <td><a name="master_walog_closer_implementation" class="prop"></a> master.walog.closer.implementation</td>
<td>A class that implements a mechansim to steal write access to a file<br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.server.master.recovery.HadoopLogCloser</code></td>
</tr>
<tr>
- <td><a name="monitor_prefix"></a> <strong>monitor.</strong>*</td>
+ <td><a name="monitor_prefix" class="prop"></a> <strong>monitor.</strong>*</td>
<td>Properties in this category affect the behavior of the monitor web server.</td>
</tr>
<tr>
- <td><a name="monitor_banner_background"></a> monitor.banner.background</td>
- <td>The background color of the banner text displayed on the monitor page.<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">#304065</code></td>
+ <td><a name="monitor_banner_background" class="prop"></a> monitor.banner.background</td>
+ <td><strong>Deprecated.</strong> <del>The background color of the banner text displayed on the monitor page.</del><br /><del><strong>type:</strong> STRING</del>, <del><strong>zk mutable:</strong> yes</del>, <del><strong>default value:</strong> <code class="highlighter-rouge">#304065</code></del></td>
</tr>
<tr>
- <td><a name="monitor_banner_color"></a> monitor.banner.color</td>
- <td>The color of the banner text displayed on the monitor page.<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">#c4c4c4</code></td>
+ <td><a name="monitor_banner_color" class="prop"></a> monitor.banner.color</td>
+ <td><strong>Deprecated.</strong> <del>The color of the banner text displayed on the monitor page.</del><br /><del><strong>type:</strong> STRING</del>, <del><strong>zk mutable:</strong> yes</del>, <del><strong>default value:</strong> <code class="highlighter-rouge">#c4c4c4</code></del></td>
</tr>
<tr>
- <td><a name="monitor_banner_text"></a> monitor.banner.text</td>
- <td>The banner text displayed on the monitor page.<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> empty</td>
+ <td><a name="monitor_banner_text" class="prop"></a> monitor.banner.text</td>
+ <td><strong>Deprecated.</strong> <del>The banner text displayed on the monitor page.</del><br /><del><strong>type:</strong> STRING</del>, <del><strong>zk mutable:</strong> yes</del>, <del><strong>default value:</strong> empty</del></td>
</tr>
<tr>
- <td><a name="monitor_lock_check_interval"></a> monitor.lock.check.interval</td>
+ <td><a name="monitor_lock_check_interval" class="prop"></a> monitor.lock.check.interval</td>
<td>The amount of time to sleep between checking for the Montior ZooKeeper lock<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">5s</code></td>
</tr>
<tr>
- <td><a name="monitor_log_date_format"></a> monitor.log.date.format</td>
+ <td><a name="monitor_log_date_format" class="prop"></a> monitor.log.date.format</td>
<td>The SimpleDateFormat string used to configure the date shown on the ‘Recent Logs’ monitor page<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">yyyy/MM/dd HH:mm:ss,SSS</code></td>
</tr>
<tr>
- <td><a name="monitor_port_client"></a> monitor.port.client</td>
+ <td><a name="monitor_port_client" class="prop"></a> monitor.port.client</td>
<td>The listening port for the monitor’s http service<br /><strong>type:</strong> PORT, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">9995</code></td>
</tr>
<tr>
- <td><a name="monitor_port_log4j"></a> monitor.port.log4j</td>
+ <td><a name="monitor_port_log4j" class="prop"></a> monitor.port.log4j</td>
<td>The listening port for the monitor’s log4j logging collection.<br /><strong>type:</strong> PORT, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">4560</code></td>
</tr>
<tr>
- <td><a name="monitor_ssl_exclude_ciphers"></a> monitor.ssl.exclude.ciphers</td>
+ <td><a name="monitor_resources_external" class="prop"></a> monitor.resources.external</td>
+ <td>A JSON Map of Strings. Each String should be an HTML tag of an external resource (JS or CSS) to be imported by the Monitor. <br />Be sure to wrap with CDATA tags. If this value is set, all of the external resources in the <head> tag of the Monitor will be replaced with <br />the tags set here. Be sure the jquery tag is first since other scripts will depend on it. The resources that are used by default can be seen in accumulo/server/monitor/src/main/resources/templates/def [...]
+ </tr>
+ <tr>
+ <td><a name="monitor_ssl_exclude_ciphers" class="prop"></a> monitor.ssl.exclude.ciphers</td>
<td>A comma-separated list of disallowed SSL Ciphers, see mmonitor.ssl.include.ciphers to allow ciphers<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="monitor_ssl_include_ciphers"></a> monitor.ssl.include.ciphers</td>
+ <td><a name="monitor_ssl_include_ciphers" class="prop"></a> monitor.ssl.include.ciphers</td>
<td>A comma-separated list of allows SSL Ciphers, see monitor.ssl.exclude.ciphers to disallow ciphers<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="monitor_ssl_include_protocols"></a> monitor.ssl.include.protocols</td>
+ <td><a name="monitor_ssl_include_protocols" class="prop"></a> monitor.ssl.include.protocols</td>
<td>A comma-separate list of allowed SSL protocols<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">TLSv1,TLSv1.1,TLSv1.2</code></td>
</tr>
<tr>
- <td><a name="monitor_ssl_keyStore"></a> monitor.ssl.keyStore</td>
+ <td><a name="monitor_ssl_keyStore" class="prop"></a> monitor.ssl.keyStore</td>
<td>The keystore for enabling monitor SSL.<br /><strong>type:</strong> PATH, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="monitor_ssl_keyStorePassword"></a> monitor.ssl.keyStorePassword</td>
+ <td><a name="monitor_ssl_keyStorePassword" class="prop"></a> monitor.ssl.keyStorePassword</td>
<td>The keystore password for enabling monitor SSL.<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="monitor_ssl_keyStoreType"></a> monitor.ssl.keyStoreType</td>
+ <td><a name="monitor_ssl_keyStoreType" class="prop"></a> monitor.ssl.keyStoreType</td>
<td>Type of SSL keystore<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">jks</code></td>
</tr>
<tr>
- <td><a name="monitor_ssl_trustStore"></a> monitor.ssl.trustStore</td>
+ <td><a name="monitor_ssl_trustStore" class="prop"></a> monitor.ssl.trustStore</td>
<td>The truststore for enabling monitor SSL.<br /><strong>type:</strong> PATH, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="monitor_ssl_trustStorePassword"></a> monitor.ssl.trustStorePassword</td>
+ <td><a name="monitor_ssl_trustStorePassword" class="prop"></a> monitor.ssl.trustStorePassword</td>
<td>The truststore password for enabling monitor SSL.<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="monitor_ssl_trustStoreType"></a> monitor.ssl.trustStoreType</td>
+ <td><a name="monitor_ssl_trustStoreType" class="prop"></a> monitor.ssl.trustStoreType</td>
<td>Type of SSL truststore<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">jks</code></td>
</tr>
<tr>
- <td><a name="replication_prefix"></a> <strong>replication.</strong>*</td>
+ <td><a name="replication_prefix" class="prop"></a> <strong>replication.</strong>*</td>
<td>Properties in this category affect the replication of data to other Accumulo instances.</td>
</tr>
<tr>
- <td><a name="replication_driver_delay"></a> replication.driver.delay</td>
+ <td><a name="replication_driver_delay" class="prop"></a> replication.driver.delay</td>
<td>Amount of time to wait before the replication work loop begins in the master.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0s</code></td>
</tr>
<tr>
- <td><a name="replication_max_unit_size"></a> replication.max.unit.size</td>
+ <td><a name="replication_max_unit_size" class="prop"></a> replication.max.unit.size</td>
<td>Maximum size of data to send in a replication message<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">64M</code></td>
</tr>
<tr>
- <td><a name="replication_max_work_queue"></a> replication.max.work.queue</td>
+ <td><a name="replication_max_work_queue" class="prop"></a> replication.max.work.queue</td>
<td>Upper bound of the number of files queued for replication<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1000</code></td>
</tr>
<tr>
- <td><a name="replication_name"></a> replication.name</td>
+ <td><a name="replication_name" class="prop"></a> replication.name</td>
<td>Name of this cluster with respect to replication. Used to identify this instance from other peers<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="replication_peer_prefix"></a> <strong>replication.peer.</strong>*</td>
+ <td><a name="replication_peer_prefix" class="prop"></a> <strong>replication.peer.</strong>*</td>
<td>Properties in this category control what systems data can be replicated to</td>
</tr>
<tr>
- <td><a name="replication_peer_keytab_prefix"></a> <strong>replication.peer.keytab.</strong>*</td>
+ <td><a name="replication_peer_keytab_prefix" class="prop"></a> <strong>replication.peer.keytab.</strong>*</td>
<td>The keytab to use when authenticating with the given peer</td>
</tr>
<tr>
- <td><a name="replication_peer_password_prefix"></a> <strong>replication.peer.password.</strong>*</td>
+ <td><a name="replication_peer_password_prefix" class="prop"></a> <strong>replication.peer.password.</strong>*</td>
<td>The password to provide when authenticating with the given peer</td>
</tr>
<tr>
- <td><a name="replication_peer_user_prefix"></a> <strong>replication.peer.user.</strong>*</td>
+ <td><a name="replication_peer_user_prefix" class="prop"></a> <strong>replication.peer.user.</strong>*</td>
<td>The username to provide when authenticating with the given peer</td>
</tr>
<tr>
- <td><a name="replication_receipt_service_port"></a> replication.receipt.service.port</td>
+ <td><a name="replication_receipt_service_port" class="prop"></a> replication.receipt.service.port</td>
<td>Listen port used by thrift service in tserver listening for replication<br /><strong>type:</strong> PORT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10002</code></td>
</tr>
<tr>
- <td><a name="replication_receiver_min_threads"></a> replication.receiver.min.threads</td>
+ <td><a name="replication_receiver_min_threads" class="prop"></a> replication.receiver.min.threads</td>
<td>Minimum number of threads for replication<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1</code></td>
</tr>
<tr>
- <td><a name="replication_receiver_threadcheck_time"></a> replication.receiver.threadcheck.time</td>
+ <td><a name="replication_receiver_threadcheck_time" class="prop"></a> replication.receiver.threadcheck.time</td>
<td>The time between adjustments of the replication thread pool.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">30s</code></td>
</tr>
<tr>
- <td><a name="replication_rpc_timeout"></a> replication.rpc.timeout</td>
+ <td><a name="replication_rpc_timeout" class="prop"></a> replication.rpc.timeout</td>
<td>Amount of time for a single replication RPC call to last before failing the attempt. See replication.work.attempts.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">2m</code></td>
</tr>
<tr>
- <td><a name="replication_trace_percent"></a> replication.trace.percent</td>
+ <td><a name="replication_trace_percent" class="prop"></a> replication.trace.percent</td>
<td>The sampling percentage to use for replication traces<br /><strong>type:</strong> FRACTION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0.1</code></td>
</tr>
<tr>
- <td><a name="replication_work_assigner"></a> replication.work.assigner</td>
+ <td><a name="replication_work_assigner" class="prop"></a> replication.work.assigner</td>
<td>Replication WorkAssigner implementation to use<br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.master.replication.UnorderedWorkAssigner</code></td>
</tr>
<tr>
- <td><a name="replication_work_assignment_sleep"></a> replication.work.assignment.sleep</td>
+ <td><a name="replication_work_assignment_sleep" class="prop"></a> replication.work.assignment.sleep</td>
<td>Amount of time to sleep between replication work assignment<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">30s</code></td>
</tr>
<tr>
- <td><a name="replication_work_attempts"></a> replication.work.attempts</td>
+ <td><a name="replication_work_attempts" class="prop"></a> replication.work.attempts</td>
<td>Number of attempts to try to replicate some data before giving up and letting it naturally be retried later<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10</code></td>
</tr>
<tr>
- <td><a name="replication_work_processor_delay"></a> replication.work.processor.delay</td>
+ <td><a name="replication_work_processor_delay" class="prop"></a> replication.work.processor.delay</td>
<td>Amount of time to wait before first checking for replication work, not useful outside of tests<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0s</code></td>
</tr>
<tr>
- <td><a name="replication_work_processor_period"></a> replication.work.processor.period</td>
+ <td><a name="replication_work_processor_period" class="prop"></a> replication.work.processor.period</td>
<td>Amount of time to wait before re-checking for replication work, not useful outside of tests<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0s</code></td>
</tr>
<tr>
- <td><a name="replication_worker_threads"></a> replication.worker.threads</td>
+ <td><a name="replication_worker_threads" class="prop"></a> replication.worker.threads</td>
<td>Size of the threadpool that each tabletserver devotes to replicating data<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">4</code></td>
</tr>
<tr>
- <td><a name="rpc_prefix"></a> <strong>rpc.</strong>*</td>
+ <td><a name="rpc_prefix" class="prop"></a> <strong>rpc.</strong>*</td>
<td>Properties in this category related to the configuration of SSL keys for RPC. See also instance.ssl.enabled</td>
</tr>
<tr>
- <td><a name="rpc_javax_net_ssl_keyStore"></a> rpc.javax.net.ssl.keyStore</td>
+ <td><a name="rpc_javax_net_ssl_keyStore" class="prop"></a> rpc.javax.net.ssl.keyStore</td>
<td>Path of the keystore file for the server’s private SSL key<br /><strong>type:</strong> PATH, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="rpc_javax_net_ssl_keyStorePassword"></a> rpc.javax.net.ssl.keyStorePassword</td>
+ <td><a name="rpc_javax_net_ssl_keyStorePassword" class="prop"></a> rpc.javax.net.ssl.keyStorePassword</td>
<td>Password used to encrypt the SSL private keystore. Leave blank to use the Accumulo instance secret<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="rpc_javax_net_ssl_keyStoreType"></a> rpc.javax.net.ssl.keyStoreType</td>
+ <td><a name="rpc_javax_net_ssl_keyStoreType" class="prop"></a> rpc.javax.net.ssl.keyStoreType</td>
<td>Type of SSL keystore<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">jks</code></td>
</tr>
<tr>
- <td><a name="rpc_javax_net_ssl_trustStore"></a> rpc.javax.net.ssl.trustStore</td>
+ <td><a name="rpc_javax_net_ssl_trustStore" class="prop"></a> rpc.javax.net.ssl.trustStore</td>
<td>Path of the truststore file for the root cert<br /><strong>type:</strong> PATH, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="rpc_javax_net_ssl_trustStorePassword"></a> rpc.javax.net.ssl.trustStorePassword</td>
+ <td><a name="rpc_javax_net_ssl_trustStorePassword" class="prop"></a> rpc.javax.net.ssl.trustStorePassword</td>
<td>Password used to encrypt the SSL truststore. Leave blank to use no password<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="rpc_javax_net_ssl_trustStoreType"></a> rpc.javax.net.ssl.trustStoreType</td>
+ <td><a name="rpc_javax_net_ssl_trustStoreType" class="prop"></a> rpc.javax.net.ssl.trustStoreType</td>
<td>Type of SSL truststore<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">jks</code></td>
</tr>
<tr>
- <td><a name="rpc_sasl_qop"></a> rpc.sasl.qop</td>
+ <td><a name="rpc_sasl_qop" class="prop"></a> rpc.sasl.qop</td>
<td>The quality of protection to be used with SASL. Valid values are ‘auth’, ‘auth-int’, and ‘auth-conf’<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">auth</code></td>
</tr>
<tr>
- <td><a name="rpc_ssl_cipher_suites"></a> rpc.ssl.cipher.suites</td>
+ <td><a name="rpc_ssl_cipher_suites" class="prop"></a> rpc.ssl.cipher.suites</td>
<td>Comma separated list of cipher suites that can be used by accepted connections<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="rpc_ssl_client_protocol"></a> rpc.ssl.client.protocol</td>
+ <td><a name="rpc_ssl_client_protocol" class="prop"></a> rpc.ssl.client.protocol</td>
<td>The protocol used to connect to a secure server, must be in the list of enabled protocols on the server side (rpc.ssl.server.enabled.protocols)<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">TLSv1</code></td>
</tr>
<tr>
- <td><a name="rpc_ssl_server_enabled_protocols"></a> rpc.ssl.server.enabled.protocols</td>
+ <td><a name="rpc_ssl_server_enabled_protocols" class="prop"></a> rpc.ssl.server.enabled.protocols</td>
<td>Comma separated list of protocols that can be used to accept connections<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">TLSv1,TLSv1.1,TLSv1.2</code></td>
</tr>
<tr>
- <td><a name="rpc_useJsse"></a> rpc.useJsse</td>
+ <td><a name="rpc_useJsse" class="prop"></a> rpc.useJsse</td>
<td>Use JSSE system properties to configure SSL rather than the rpc.javax.net.ssl.* Accumulo properties<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="table_prefix"></a> <strong>table.</strong>*</td>
+ <td><a name="table_prefix" class="prop"></a> <strong>table.</strong>*</td>
<td>Properties in this category affect tablet server treatment of tablets, but can be configured on a per-table basis. Setting these properties in the site file will override the default globally for all tables and not any specific table. However, both the default and the global setting can be overridden per table using the table operations API or in the shell, which sets the overridden value in zookeeper. Restarting accumulo tablet servers after setting these properties in the sit [...]
</tr>
<tr>
- <td><a name="table_balancer"></a> table.balancer</td>
+ <td><a name="table_balancer" class="prop"></a> table.balancer</td>
<td>This property can be set to allow the LoadBalanceByTable load balancer to change the called Load Balancer for this table<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.server.master.balancer.DefaultLoadBalancer</code></td>
</tr>
<tr>
- <td><a name="table_bloom_enabled"></a> table.bloom.enabled</td>
+ <td><a name="table_bloom_enabled" class="prop"></a> table.bloom.enabled</td>
<td>Use bloom filters on this table.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="table_bloom_error_rate"></a> table.bloom.error.rate</td>
+ <td><a name="table_bloom_error_rate" class="prop"></a> table.bloom.error.rate</td>
<td>Bloom filter error rate.<br /><strong>type:</strong> FRACTION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0.5%</code></td>
</tr>
<tr>
- <td><a name="table_bloom_hash_type"></a> table.bloom.hash.type</td>
+ <td><a name="table_bloom_hash_type" class="prop"></a> table.bloom.hash.type</td>
<td>The bloom filter hash type<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">murmur</code></td>
</tr>
<tr>
- <td><a name="table_bloom_key_functor"></a> table.bloom.key.functor</td>
+ <td><a name="table_bloom_key_functor" class="prop"></a> table.bloom.key.functor</td>
<td>A function that can transform the key prior to insertion and check of bloom filter. org.apache.accumulo.core.file.keyfunctor.RowFunctor,,org.apache.accumulo.core.file.keyfunctor.ColumnFamilyFunctor, and org.apache.accumulo.core.file.keyfunctor.ColumnQualifierFunctor are allowable values. One can extend any of the above mentioned classes to perform specialized parsing of the key. <br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> yes, <strong>default value:</st [...]
</tr>
<tr>
- <td><a name="table_bloom_load_threshold"></a> table.bloom.load.threshold</td>
+ <td><a name="table_bloom_load_threshold" class="prop"></a> table.bloom.load.threshold</td>
<td>This number of seeks that would actually use a bloom filter must occur before a file’s bloom filter is loaded. Set this to zero to initiate loading of bloom filters when a file is opened.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1</code></td>
</tr>
<tr>
- <td><a name="table_bloom_size"></a> table.bloom.size</td>
+ <td><a name="table_bloom_size" class="prop"></a> table.bloom.size</td>
<td>Bloom filter size, as number of keys.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1048576</code></td>
</tr>
<tr>
- <td><a name="table_cache_block_enable"></a> table.cache.block.enable</td>
+ <td><a name="table_cache_block_enable" class="prop"></a> table.cache.block.enable</td>
<td>Determines whether file block cache is enabled.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="table_cache_index_enable"></a> table.cache.index.enable</td>
+ <td><a name="table_cache_index_enable" class="prop"></a> table.cache.index.enable</td>
<td>Determines whether index cache is enabled.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">true</code></td>
</tr>
<tr>
- <td><a name="table_classpath_context"></a> table.classpath.context</td>
+ <td><a name="table_classpath_context" class="prop"></a> table.classpath.context</td>
<td>Per table classpath context<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="table_compaction_major_everything_idle"></a> table.compaction.major.everything.idle</td>
+ <td><a name="table_compaction_major_everything_idle" class="prop"></a> table.compaction.major.everything.idle</td>
<td>After a tablet has been idle (no mutations) for this time period it may have all of its files compacted into one. There is no guarantee an idle tablet will be compacted. Compactions of idle tablets are only started when regular compactions are not running. Idle compactions only take place for tablets that have one or more files.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1h</code></td>
</tr>
<tr>
- <td><a name="table_compaction_major_ratio"></a> table.compaction.major.ratio</td>
+ <td><a name="table_compaction_major_ratio" class="prop"></a> table.compaction.major.ratio</td>
<td>minimum ratio of total input size to maximum input file size for running a major compactionWhen adjusting this property you may want to also adjust table.file.max. Want to avoid the situation where only merging minor compactions occur.<br /><strong>type:</strong> FRACTION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">3</code></td>
</tr>
<tr>
- <td><a name="table_compaction_minor_idle"></a> table.compaction.minor.idle</td>
+ <td><a name="table_compaction_minor_idle" class="prop"></a> table.compaction.minor.idle</td>
<td>After a tablet has been idle (no mutations) for this time period it may have its in-memory map flushed to disk in a minor compaction. There is no guarantee an idle tablet will be compacted.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5m</code></td>
</tr>
<tr>
- <td><a name="table_compaction_minor_logs_threshold"></a> table.compaction.minor.logs.threshold</td>
+ <td><a name="table_compaction_minor_logs_threshold" class="prop"></a> table.compaction.minor.logs.threshold</td>
<td>When there are more than this many write-ahead logs against a tablet, it will be minor compacted. See comment for property tserver.memory.maps.max<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">3</code></td>
</tr>
<tr>
- <td><a name="table_compaction_minor_merge_file_size_max"></a> table.compaction.minor.merge.file.size.max</td>
+ <td><a name="table_compaction_minor_merge_file_size_max" class="prop"></a> table.compaction.minor.merge.file.size.max</td>
<td>The max file size used for a merging minor compaction. The default value of 0 disables a max file size.<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0</code></td>
</tr>
<tr>
- <td><a name="table_constraint_prefix"></a> <strong>table.constraint.</strong>*</td>
+ <td><a name="table_constraint_prefix" class="prop"></a> <strong>table.constraint.</strong>*</td>
<td>Properties in this category are per-table properties that add constraints to a table. These properties start with the category prefix, followed by a number, and their values correspond to a fully qualified Java class that implements the Constraint interface.<br />For example:<br />table.constraint.1 = org.apache.accumulo.core.constraints.MyCustomConstraint<br />and:<br />table.constraint.2 = my.package.constraints.MySecondConstraint</td>
</tr>
<tr>
- <td><a name="table_custom_prefix"></a> <strong>table.custom.</strong>*</td>
+ <td><a name="table_custom_prefix" class="prop"></a> <strong>table.custom.</strong>*</td>
<td>Prefix to be used for user defined arbitrary properties.</td>
</tr>
<tr>
- <td><a name="table_durability"></a> table.durability</td>
+ <td><a name="table_durability" class="prop"></a> table.durability</td>
<td>The durability used to write to the write-ahead log. Legal values are: none, which skips the write-ahead log; log, which sends the data to the write-ahead log, but does nothing to make it durable; flush, which pushes data to the file system; and sync, which ensures the data is written to disk.<br /><strong>type:</strong> DURABILITY, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">sync</code></td>
</tr>
<tr>
- <td><a name="table_failures_ignore"></a> table.failures.ignore</td>
+ <td><a name="table_failures_ignore" class="prop"></a> table.failures.ignore</td>
<td>If you want queries for your table to hang or fail when data is missing from the system, then set this to false. When this set to true missing data will be reported but queries will still run possibly returning a subset of the data.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="table_file_blocksize"></a> table.file.blocksize</td>
+ <td><a name="table_file_blocksize" class="prop"></a> table.file.blocksize</td>
<td>Overrides the hadoop dfs.block.size setting so that files have better query performance. The maximum value for this is 2147483647<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0B</code></td>
</tr>
<tr>
- <td><a name="table_file_compress_blocksize"></a> table.file.compress.blocksize</td>
+ <td><a name="table_file_compress_blocksize" class="prop"></a> table.file.compress.blocksize</td>
<td>Similar to the hadoop io.seqfile.compress.blocksize setting, so that files have better query performance. The maximum value for this is 2147483647. (This setting is the size threshold prior to compression, and applies even compression is disabled.)<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">100K</code></td>
</tr>
<tr>
- <td><a name="table_file_compress_blocksize_index"></a> table.file.compress.blocksize.index</td>
+ <td><a name="table_file_compress_blocksize_index" class="prop"></a> table.file.compress.blocksize.index</td>
<td>Determines how large index blocks can be in files that support multilevel indexes. The maximum value for this is 2147483647. (This setting is the size threshold prior to compression, and applies even compression is disabled.)<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">128K</code></td>
</tr>
<tr>
- <td><a name="table_file_compress_type"></a> table.file.compress.type</td>
+ <td><a name="table_file_compress_type" class="prop"></a> table.file.compress.type</td>
<td>One of gz,snappy,lzo,none<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">gz</code></td>
</tr>
<tr>
- <td><a name="table_file_max"></a> table.file.max</td>
+ <td><a name="table_file_max" class="prop"></a> table.file.max</td>
<td>Determines the max # of files each tablet in a table can have. When adjusting this property you may want to consider adjusting table.compaction.major.ratio also. Setting this property to 0 will make it default to tserver.scan.files.open.max-1, this will prevent a tablet from having more files than can be opened. Setting this property low may throttle ingest and increase query performance.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value [...]
</tr>
<tr>
- <td><a name="table_file_replication"></a> table.file.replication</td>
+ <td><a name="table_file_replication" class="prop"></a> table.file.replication</td>
<td>Determines how many replicas to keep of a tables’ files in HDFS. When this value is LTE 0, HDFS defaults are used.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0</code></td>
</tr>
<tr>
- <td><a name="table_file_summary_maxSize"></a> table.file.summary.maxSize</td>
+ <td><a name="table_file_summary_maxSize" class="prop"></a> table.file.summary.maxSize</td>
<td>The maximum size summary that will be stored. The number of files that had summary data exceeding this threshold is reported by Summary.getFileStatistics().getLarge(). When adjusting this consider the expected number files with summaries on each tablet server and the summary cache size.<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">256K</code></td>
</tr>
<tr>
- <td><a name="table_file_type"></a> table.file.type</td>
+ <td><a name="table_file_type" class="prop"></a> table.file.type</td>
<td>Change the type of file a table writes<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">rf</code></td>
</tr>
<tr>
- <td><a name="table_formatter"></a> table.formatter</td>
+ <td><a name="table_formatter" class="prop"></a> table.formatter</td>
<td>The Formatter class to apply on results in the shell<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.core.util.format.DefaultFormatter</code></td>
</tr>
<tr>
- <td><a name="table_group_prefix"></a> <strong>table.group.</strong>*</td>
+ <td><a name="table_group_prefix" class="prop"></a> <strong>table.group.</strong>*</td>
<td>Properties in this category are per-table properties that define locality groups in a table. These properties start with the category prefix, followed by a name, followed by a period, and followed by a property for that group.<br />For example table.group.group1=x,y,z sets the column families for a group called group1. Once configured, group1 can be enabled by adding it to the list of groups in the table.groups.enabled property.<br />Additional group options may be specified fo [...]
</tr>
<tr>
- <td><a name="table_groups_enabled"></a> table.groups.enabled</td>
+ <td><a name="table_groups_enabled" class="prop"></a> table.groups.enabled</td>
<td>A comma separated list of locality group names to enable for this table.<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> empty</td>
</tr>
<tr>
- <td><a name="table_interepreter"></a> table.interepreter</td>
+ <td><a name="table_interepreter" class="prop"></a> table.interepreter</td>
<td>The ScanInterpreter class to apply on scan arguments in the shell<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.core.util.interpret.DefaultScanInterpreter</code></td>
</tr>
<tr>
- <td><a name="table_iterator_prefix"></a> <strong>table.iterator.</strong>*</td>
+ <td><a name="table_iterator_prefix" class="prop"></a> <strong>table.iterator.</strong>*</td>
<td>Properties in this category specify iterators that are applied at various stages (scopes) of interaction with a table. These properties start with the category prefix, followed by a scope (minc, majc, scan, etc.), followed by a period, followed by a name, as in table.iterator.scan.vers, or table.iterator.scan.custom. The values for these properties are a number indicating the ordering in which it is applied, and a class name such as:<br /> table.iterator.scan.vers = 10,org.apac [...]
</tr>
<tr>
- <td><a name="table_iterator_majc_prefix"></a> <strong>table.iterator.majc.</strong>*</td>
+ <td><a name="table_iterator_majc_prefix" class="prop"></a> <strong>table.iterator.majc.</strong>*</td>
<td>Convenience prefix to find options for the majc iterator scope</td>
</tr>
<tr>
- <td><a name="table_iterator_minc_prefix"></a> <strong>table.iterator.minc.</strong>*</td>
+ <td><a name="table_iterator_minc_prefix" class="prop"></a> <strong>table.iterator.minc.</strong>*</td>
<td>Convenience prefix to find options for the minc iterator scope</td>
</tr>
<tr>
- <td><a name="table_iterator_scan_prefix"></a> <strong>table.iterator.scan.</strong>*</td>
+ <td><a name="table_iterator_scan_prefix" class="prop"></a> <strong>table.iterator.scan.</strong>*</td>
<td>Convenience prefix to find options for the scan iterator scope</td>
</tr>
<tr>
- <td><a name="table_majc_compaction_strategy"></a> table.majc.compaction.strategy</td>
+ <td><a name="table_majc_compaction_strategy" class="prop"></a> table.majc.compaction.strategy</td>
<td>A customizable major compaction strategy.<br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.tserver.compaction.DefaultCompactionStrategy</code></td>
</tr>
<tr>
- <td><a name="table_majc_compaction_strategy_opts_prefix"></a> <strong>table.majc.compaction.strategy.opts.</strong>*</td>
+ <td><a name="table_majc_compaction_strategy_opts_prefix" class="prop"></a> <strong>table.majc.compaction.strategy.opts.</strong>*</td>
<td>Properties in this category are used to configure the compaction strategy.</td>
</tr>
<tr>
- <td><a name="table_replication"></a> table.replication</td>
+ <td><a name="table_replication" class="prop"></a> table.replication</td>
<td>Is replication enabled for the given table<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="table_replication_target_prefix"></a> <strong>table.replication.target.</strong>*</td>
+ <td><a name="table_replication_target_prefix" class="prop"></a> <strong>table.replication.target.</strong>*</td>
<td>Enumerate a mapping of other systems which this table should replicate their data to. The key suffix is the identifying cluster name and the value is an identifier for a location on the target system, e.g. the ID of the table on the target to replicate to</td>
</tr>
<tr>
- <td><a name="table_sampler"></a> table.sampler</td>
+ <td><a name="table_sampler" class="prop"></a> table.sampler</td>
<td>The name of a class that implements org.apache.accumulo.core.Sampler. Setting this option enables storing a sample of data which can be scanned. Always having a current sample can useful for query optimization and data comprehension. After enabling sampling for an existing table, a compaction is needed to compute the sample for existing data. The compact command in the shell has an option to only compact files without sample data.<br /><strong>type:</strong> CLASSNAME, <st [...]
</tr>
<tr>
- <td><a name="table_sampler_opt_prefix"></a> <strong>table.sampler.opt.</strong>*</td>
+ <td><a name="table_sampler_opt_prefix" class="prop"></a> <strong>table.sampler.opt.</strong>*</td>
<td>The property is used to set options for a sampler. If a sample had two options like hasher and modulous, then the two properties table.sampler.opt.hasher=${hash algorithm} and table.sampler.opt.modulous=${mod} would be set.</td>
</tr>
<tr>
- <td><a name="table_scan_max_memory"></a> table.scan.max.memory</td>
+ <td><a name="table_scan_max_memory" class="prop"></a> table.scan.max.memory</td>
<td>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="highlighter-rouge">512K</code></td>
</tr>
<tr>
- <td><a name="table_security_scan_visibility_default"></a> table.security.scan.visibility.default</td>
+ <td><a name="table_security_scan_visibility_default" class="prop"></a> table.security.scan.visibility.default</td>
<td>The security label that will be assumed at scan time if an entry does not have a visibility set.<br />Note: An empty security label is displayed as []. The scan results will show an empty visibility even if the visibility from this setting is applied to the entry.<br />CAUTION: If a particular key has an empty security label AND its table’s default visibility is also empty, access will ALWAYS be granted for users with permission to that table. Additionally, if this field is cha [...]
</tr>
<tr>
- <td><a name="table_split_endrow_size_max"></a> table.split.endrow.size.max</td>
+ <td><a name="table_split_endrow_size_max" class="prop"></a> table.split.endrow.size.max</td>
<td>Maximum size of end row<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10K</code></td>
</tr>
<tr>
- <td><a name="table_split_threshold"></a> table.split.threshold</td>
+ <td><a name="table_split_threshold" class="prop"></a> table.split.threshold</td>
<td>When combined size of files exceeds this amount a tablet is split.<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1G</code></td>
</tr>
<tr>
- <td><a name="table_summarizer_prefix"></a> <strong>table.summarizer.</strong>*</td>
+ <td><a name="table_summarizer_prefix" class="prop"></a> <strong>table.summarizer.</strong>*</td>
<td>Prefix for configuring summarizers for a table. Using this prefix multiple summarizers can be configured with options for each one. Each summarizer configured should have a unique id, this id can be anything. To add a summarizer set table.summarizer.<unique>=<summarizer class="" name="">. If the summarizer has options, then for each option set table.summarizer.<unique>.opt.<key>=<value>.</value></key></unique></summarizer></unique></td>
</tr>
<tr>
- <td><a name="table_suspend_duration"></a> table.suspend.duration</td>
+ <td><a name="table_suspend_duration" class="prop"></a> table.suspend.duration</td>
<td>For tablets belonging to this table: When a tablet server dies, allow the tablet server this duration to revive before reassigning its tabletsto other tablet servers.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0s</code></td>
</tr>
<tr>
- <td><a name="table_walog_enabled"></a> table.walog.enabled</td>
+ <td><a name="table_walog_enabled" class="prop"></a> table.walog.enabled</td>
<td><strong>Deprecated.</strong> <del>This setting is deprecated. Use table.durability=none instead.</del><br /><del><strong>type:</strong> BOOLEAN</del>, <del><strong>zk mutable:</strong> yes</del>, <del><strong>default value:</strong> <code class="highlighter-rouge">true</code></del></td>
</tr>
<tr>
- <td><a name="trace_prefix"></a> <strong>trace.</strong>*</td>
+ <td><a name="trace_prefix" class="prop"></a> <strong>trace.</strong>*</td>
<td>Properties in this category affect the behavior of distributed tracing.</td>
</tr>
<tr>
- <td><a name="trace_password"></a> trace.password</td>
+ <td><a name="trace_password" class="prop"></a> trace.password</td>
<td>The password for the user used to store distributed traces<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">secret</code></td>
</tr>
<tr>
- <td><a name="trace_port_client"></a> trace.port.client</td>
+ <td><a name="trace_port_client" class="prop"></a> trace.port.client</td>
<td>The listening port for the trace server<br /><strong>type:</strong> PORT, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">12234</code></td>
</tr>
<tr>
- <td><a name="trace_span_receiver_prefix"></a> <strong>trace.span.receiver.</strong>*</td>
+ <td><a name="trace_span_receiver_prefix" class="prop"></a> <strong>trace.span.receiver.</strong>*</td>
<td>Prefix for span receiver configuration properties</td>
</tr>
<tr>
- <td><a name="trace_span_receivers"></a> trace.span.receivers</td>
+ <td><a name="trace_span_receivers" class="prop"></a> trace.span.receivers</td>
<td>A list of span receiver classes to send trace spans<br /><strong>type:</strong> CLASSNAMELIST, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.tracer.ZooTraceClient</code></td>
</tr>
<tr>
- <td><a name="trace_table"></a> trace.table</td>
+ <td><a name="trace_table" class="prop"></a> trace.table</td>
<td>The name of the table to store distributed traces<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">trace</code></td>
</tr>
<tr>
- <td><a name="trace_token_property_prefix"></a> <strong>trace.token.property.</strong>*</td>
+ <td><a name="trace_token_property_prefix" class="prop"></a> <strong>trace.token.property.</strong>*</td>
<td>The prefix used to create a token for storing distributed traces. For each property required by trace.token.type, place this prefix in front of it.</td>
</tr>
<tr>
- <td><a name="trace_token_type"></a> trace.token.type</td>
+ <td><a name="trace_token_type" class="prop"></a> trace.token.type</td>
<td>An AuthenticationToken type supported by the authorizer<br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.core.client.security.tokens.PasswordToken</code></td>
</tr>
<tr>
- <td><a name="trace_user"></a> trace.user</td>
+ <td><a name="trace_user" class="prop"></a> trace.user</td>
<td>The name of the user to store distributed traces<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">root</code></td>
</tr>
<tr>
- <td><a name="trace_zookeeper_path"></a> trace.zookeeper.path</td>
+ <td><a name="trace_zookeeper_path" class="prop"></a> trace.zookeeper.path</td>
<td>The zookeeper node where tracers are registered<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> no, <strong>default value:</strong> <code class="highlighter-rouge">/tracers</code></td>
</tr>
<tr>
- <td><a name="tserver_prefix"></a> <strong>tserver.</strong>*</td>
+ <td><a name="tserver_prefix" class="prop"></a> <strong>tserver.</strong>*</td>
<td>Properties in this category affect the behavior of the tablet servers</td>
</tr>
<tr>
- <td><a name="tserver_archive_walogs"></a> tserver.archive.walogs</td>
+ <td><a name="tserver_archive_walogs" class="prop"></a> tserver.archive.walogs</td>
<td>Keep copies of the WALOGs for debugging purposes<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="tserver_assignment_concurrent_max"></a> tserver.assignment.concurrent.max</td>
+ <td><a name="tserver_assignment_concurrent_max" class="prop"></a> tserver.assignment.concurrent.max</td>
<td>The number of threads available to load tablets. Recoveries are still performed serially.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">2</code></td>
</tr>
<tr>
- <td><a name="tserver_assignment_duration_warning"></a> tserver.assignment.duration.warning</td>
+ <td><a name="tserver_assignment_duration_warning" class="prop"></a> tserver.assignment.duration.warning</td>
<td>The amount of time an assignment can run before the server will print a warning along with the current stack trace. Meant to help debug stuck assignments<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10m</code></td>
</tr>
<tr>
- <td><a name="tserver_bloom_load_concurrent_max"></a> tserver.bloom.load.concurrent.max</td>
+ <td><a name="tserver_bloom_load_concurrent_max" class="prop"></a> tserver.bloom.load.concurrent.max</td>
<td>The number of concurrent threads that will load bloom filters in the background. Setting this to zero will make bloom filters load in the foreground.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">4</code></td>
</tr>
<tr>
- <td><a name="tserver_bulk_assign_threads"></a> tserver.bulk.assign.threads</td>
+ <td><a name="tserver_bulk_assign_threads" class="prop"></a> tserver.bulk.assign.threads</td>
<td>The master delegates bulk file processing and assignment to tablet servers. After the bulk file has been processed, the tablet server will assign the file to the appropriate tablets on all servers. This property controls the number of threads used to communicate to the other servers.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1</code></td>
</tr>
<tr>
- <td><a name="tserver_bulk_process_threads"></a> tserver.bulk.process.threads</td>
+ <td><a name="tserver_bulk_process_threads" class="prop"></a> tserver.bulk.process.threads</td>
<td>The master will task a tablet server with pre-processing a bulk file prior to assigning it to the appropriate tablet servers. This configuration value controls the number of threads used to process the files.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1</code></td>
</tr>
<tr>
- <td><a name="tserver_bulk_retry_max"></a> tserver.bulk.retry.max</td>
+ <td><a name="tserver_bulk_retry_max" class="prop"></a> tserver.bulk.retry.max</td>
<td>The number of times the tablet server will attempt to assign a file to a tablet as it migrates and splits.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5</code></td>
</tr>
<tr>
- <td><a name="tserver_bulk_timeout"></a> tserver.bulk.timeout</td>
+ <td><a name="tserver_bulk_timeout" class="prop"></a> tserver.bulk.timeout</td>
<td>The time to wait for a tablet server to process a bulk import request.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5m</code></td>
</tr>
<tr>
- <td><a name="tserver_cache_data_size"></a> tserver.cache.data.size</td>
+ <td><a name="tserver_cache_data_size" class="prop"></a> tserver.cache.data.size</td>
<td>Specifies the size of the cache for file data blocks.<br /><strong>type:</strong> MEMORY, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10%</code></td>
</tr>
<tr>
- <td><a name="tserver_cache_index_size"></a> tserver.cache.index.size</td>
+ <td><a name="tserver_cache_index_size" class="prop"></a> tserver.cache.index.size</td>
<td>Specifies the size of the cache for file indices.<br /><strong>type:</strong> MEMORY, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">25%</code></td>
</tr>
<tr>
- <td><a name="tserver_cache_policy"></a> tserver.cache.policy</td>
- <td>Specifies the eviction policy of the file data caches (LRU or TinyLFU).<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">LRU</code></td>
+ <td><a name="tserver_cache_manager_class" class="prop"></a> tserver.cache.manager.class</td>
+ <td>Specifies the class name of the block cache factory implementation. Alternative implementation is org.apache.accumulo.core.file.blockfile.cache.tinylfu.TinyLfuBlockCacheManager<br /><strong>type:</strong> STRING, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.core.file.blockfile.cache.lru.LruBlockCacheManager</code></td>
</tr>
<tr>
- <td><a name="tserver_cache_summary_size"></a> tserver.cache.summary.size</td>
+ <td><a name="tserver_cache_summary_size" class="prop"></a> tserver.cache.summary.size</td>
<td>Specifies the size of the cache for summary data on each tablet server.<br /><strong>type:</strong> MEMORY, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10%</code></td>
</tr>
<tr>
- <td><a name="tserver_client_timeout"></a> tserver.client.timeout</td>
+ <td><a name="tserver_client_timeout" class="prop"></a> tserver.client.timeout</td>
<td>Time to wait for clients to continue scans before closing a session.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">3s</code></td>
</tr>
<tr>
- <td><a name="tserver_compaction_major_concurrent_max"></a> tserver.compaction.major.concurrent.max</td>
+ <td><a name="tserver_compaction_major_concurrent_max" class="prop"></a> tserver.compaction.major.concurrent.max</td>
<td>The maximum number of concurrent major compactions for a tablet server<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">3</code></td>
</tr>
<tr>
- <td><a name="tserver_compaction_major_delay"></a> tserver.compaction.major.delay</td>
+ <td><a name="tserver_compaction_major_delay" class="prop"></a> tserver.compaction.major.delay</td>
<td>Time a tablet server will sleep between checking which tablets need compaction.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">30s</code></td>
</tr>
<tr>
- <td><a name="tserver_compaction_major_thread_files_open_max"></a> tserver.compaction.major.thread.files.open.max</td>
+ <td><a name="tserver_compaction_major_thread_files_open_max" class="prop"></a> tserver.compaction.major.thread.files.open.max</td>
<td>Max number of files a major compaction thread can open at once. <br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10</code></td>
</tr>
<tr>
- <td><a name="tserver_compaction_major_throughput"></a> tserver.compaction.major.throughput</td>
+ <td><a name="tserver_compaction_major_throughput" class="prop"></a> tserver.compaction.major.throughput</td>
<td>Maximum number of bytes to read or write per second over all major compactions on a TabletServer, or 0B for unlimited.<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0B</code></td>
</tr>
<tr>
- <td><a name="tserver_compaction_major_trace_percent"></a> tserver.compaction.major.trace.percent</td>
+ <td><a name="tserver_compaction_major_trace_percent" class="prop"></a> tserver.compaction.major.trace.percent</td>
<td>The percent of major compactions to trace<br /><strong>type:</strong> FRACTION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0.1</code></td>
</tr>
<tr>
- <td><a name="tserver_compaction_minor_concurrent_max"></a> tserver.compaction.minor.concurrent.max</td>
+ <td><a name="tserver_compaction_minor_concurrent_max" class="prop"></a> tserver.compaction.minor.concurrent.max</td>
<td>The maximum number of concurrent minor compactions for a tablet server<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">4</code></td>
</tr>
<tr>
- <td><a name="tserver_compaction_minor_trace_percent"></a> tserver.compaction.minor.trace.percent</td>
+ <td><a name="tserver_compaction_minor_trace_percent" class="prop"></a> tserver.compaction.minor.trace.percent</td>
<td>The percent of minor compactions to trace<br /><strong>type:</strong> FRACTION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0.1</code></td>
</tr>
<tr>
- <td><a name="tserver_compaction_warn_time"></a> tserver.compaction.warn.time</td>
+ <td><a name="tserver_compaction_warn_time" class="prop"></a> tserver.compaction.warn.time</td>
<td>When a compaction has not made progress for this time period, a warning will be logged<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10m</code></td>
</tr>
<tr>
- <td><a name="tserver_default_blocksize"></a> tserver.default.blocksize</td>
+ <td><a name="tserver_default_blocksize" class="prop"></a> tserver.default.blocksize</td>
<td>Specifies a default blocksize for the tserver caches<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1M</code></td>
</tr>
<tr>
- <td><a name="tserver_dir_memdump"></a> tserver.dir.memdump</td>
+ <td><a name="tserver_dir_memdump" class="prop"></a> tserver.dir.memdump</td>
<td>A long running scan could possibly hold memory that has been minor compacted. To prevent this, the in memory map is dumped to a local file and the scan is switched to that local file. We can not switch to the minor compacted file because it may have been modified by iterators. The file dumped to the local dir is an exact copy of what was in memory.<br /><strong>type:</strong> PATH, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge" [...]
</tr>
<tr>
- <td><a name="tserver_files_open_idle"></a> tserver.files.open.idle</td>
+ <td><a name="tserver_files_open_idle" class="prop"></a> tserver.files.open.idle</td>
<td>Tablet servers leave previously used files open for future queries. This setting determines how much time an unused file should be kept open until it is closed.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1m</code></td>
</tr>
<tr>
- <td><a name="tserver_hold_time_max"></a> tserver.hold.time.max</td>
+ <td><a name="tserver_hold_time_max" class="prop"></a> tserver.hold.time.max</td>
<td>The maximum time for a tablet server to be in the “memory full” state. If the tablet server cannot write out memory in this much time, it will assume there is some failure local to its node, and quit. A value of zero is equivalent to forever.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5m</code></td>
</tr>
<tr>
- <td><a name="tserver_memory_manager"></a> tserver.memory.manager</td>
+ <td><a name="tserver_memory_manager" class="prop"></a> tserver.memory.manager</td>
<td>An implementation of MemoryManger that accumulo will use.<br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.server.tabletserver.LargestFirstMemoryManager</code></td>
</tr>
<tr>
- <td><a name="tserver_memory_maps_max"></a> tserver.memory.maps.max</td>
+ <td><a name="tserver_memory_maps_max" class="prop"></a> tserver.memory.maps.max</td>
<td>Maximum amount of memory that can be used to buffer data written to a tablet server. There are two other properties that can effectively limit memory usage table.compaction.minor.logs.threshold and tserver.walog.max.size. Ensure that table.compaction.minor.logs.threshold * tserver.walog.max.size >= this property.<br /><strong>type:</strong> MEMORY, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">33%</code></td>
</tr>
<tr>
- <td><a name="tserver_memory_maps_native_enabled"></a> tserver.memory.maps.native.enabled</td>
+ <td><a name="tserver_memory_maps_native_enabled" class="prop"></a> tserver.memory.maps.native.enabled</td>
<td>An in-memory data store for accumulo implemented in c++ that increases the amount of data accumulo can hold in memory and avoids Java GC pauses.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes but requires restart of the tserver, <strong>default value:</strong> <code class="highlighter-rouge">true</code></td>
</tr>
<tr>
- <td><a name="tserver_metadata_readahead_concurrent_max"></a> tserver.metadata.readahead.concurrent.max</td>
+ <td><a name="tserver_metadata_readahead_concurrent_max" class="prop"></a> tserver.metadata.readahead.concurrent.max</td>
<td>The maximum number of concurrent metadata read ahead that will execute.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">8</code></td>
</tr>
<tr>
- <td><a name="tserver_migrations_concurrent_max"></a> tserver.migrations.concurrent.max</td>
+ <td><a name="tserver_migrations_concurrent_max" class="prop"></a> tserver.migrations.concurrent.max</td>
<td>The maximum number of concurrent tablet migrations for a tablet server<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1</code></td>
</tr>
<tr>
- <td><a name="tserver_monitor_fs"></a> tserver.monitor.fs</td>
+ <td><a name="tserver_monitor_fs" class="prop"></a> tserver.monitor.fs</td>
<td>When enabled the tserver will monitor file systems and kill itself when one switches from rw to ro. This is usually and indication that Linux has detected a bad disk.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">true</code></td>
</tr>
<tr>
- <td><a name="tserver_mutation_queue_max"></a> tserver.mutation.queue.max</td>
+ <td><a name="tserver_mutation_queue_max" class="prop"></a> tserver.mutation.queue.max</td>
<td><strong>Deprecated.</strong> <del>This setting is deprecated. See tserver.total.mutation.queue.max. The amount of memory to use to store write-ahead-log mutations-per-session before flushing them. Since the buffer is per write session, consider the max number of concurrent writer when configuring. When using Hadoop 2, Accumulo will call hsync() on the WAL . For a small number of concurrent writers, increasing this buffer size decreases the frequncy of hsync calls. For a large n [...]
</tr>
<tr>
- <td><a name="tserver_port_client"></a> tserver.port.client</td>
+ <td><a name="tserver_port_client" class="prop"></a> tserver.port.client</td>
<td>The port used for handling client connections on the tablet servers<br /><strong>type:</strong> PORT, <strong>zk mutable:</strong> yes but requires restart of the tserver, <strong>default value:</strong> <code class="highlighter-rouge">9997</code></td>
</tr>
<tr>
- <td><a name="tserver_port_search"></a> tserver.port.search</td>
+ <td><a name="tserver_port_search" class="prop"></a> tserver.port.search</td>
<td>if the ports above are in use, search higher ports until one is available<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">false</code></td>
</tr>
<tr>
- <td><a name="tserver_readahead_concurrent_max"></a> tserver.readahead.concurrent.max</td>
+ <td><a name="tserver_readahead_concurrent_max" class="prop"></a> tserver.readahead.concurrent.max</td>
<td>The maximum number of concurrent read ahead that will execute. This effectively limits the number of long running scans that can run concurrently per tserver.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">16</code></td>
</tr>
<tr>
- <td><a name="tserver_recovery_concurrent_max"></a> tserver.recovery.concurrent.max</td>
+ <td><a name="tserver_recovery_concurrent_max" class="prop"></a> tserver.recovery.concurrent.max</td>
<td>The maximum number of threads to use to sort logs during recovery<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">2</code></td>
</tr>
<tr>
- <td><a name="tserver_replication_batchwriter_replayer_memory"></a> tserver.replication.batchwriter.replayer.memory</td>
+ <td><a name="tserver_replication_batchwriter_replayer_memory" class="prop"></a> tserver.replication.batchwriter.replayer.memory</td>
<td>Memory to provide to batchwriter to replay mutations for replication<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">50M</code></td>
</tr>
<tr>
- <td><a name="tserver_replication_default_replayer"></a> tserver.replication.default.replayer</td>
+ <td><a name="tserver_replication_default_replayer" class="prop"></a> tserver.replication.default.replayer</td>
<td>Default AccumuloReplicationReplayer implementation<br /><strong>type:</strong> CLASSNAME, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">org.apache.accumulo.tserver.replication.BatchWriterReplicationReplayer</code></td>
</tr>
<tr>
- <td><a name="tserver_replication_replayer_prefix"></a> <strong>tserver.replication.replayer.</strong>*</td>
+ <td><a name="tserver_replication_replayer_prefix" class="prop"></a> <strong>tserver.replication.replayer.</strong>*</td>
<td>Allows configuration of implementation used to apply replicated data</td>
</tr>
<tr>
- <td><a name="tserver_scan_files_open_max"></a> tserver.scan.files.open.max</td>
+ <td><a name="tserver_scan_files_open_max" class="prop"></a> tserver.scan.files.open.max</td>
<td>Maximum total files that all tablets in a tablet server can open for scans. <br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes but requires restart of the tserver, <strong>default value:</strong> <code class="highlighter-rouge">100</code></td>
</tr>
<tr>
- <td><a name="tserver_server_message_size_max"></a> tserver.server.message.size.max</td>
+ <td><a name="tserver_server_message_size_max" class="prop"></a> tserver.server.message.size.max</td>
<td>The maximum size of a message that can be sent to a tablet server.<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1G</code></td>
</tr>
<tr>
- <td><a name="tserver_server_threadcheck_time"></a> tserver.server.threadcheck.time</td>
+ <td><a name="tserver_server_threadcheck_time" class="prop"></a> tserver.server.threadcheck.time</td>
<td>The time between adjustments of the server thread pool.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1s</code></td>
</tr>
<tr>
- <td><a name="tserver_server_threads_minimum"></a> tserver.server.threads.minimum</td>
+ <td><a name="tserver_server_threads_minimum" class="prop"></a> tserver.server.threads.minimum</td>
<td>The minimum number of threads to use to handle incoming requests.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">20</code></td>
</tr>
<tr>
- <td><a name="tserver_session_idle_max"></a> tserver.session.idle.max</td>
+ <td><a name="tserver_session_idle_max" class="prop"></a> tserver.session.idle.max</td>
<td>When a tablet server’s SimpleTimer thread triggers to check idle sessions, this configurable option will be used to evaluate scan sessions to determine if they can be closed due to inactivity<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1m</code></td>
</tr>
<tr>
- <td><a name="tserver_session_update_idle_max"></a> tserver.session.update.idle.max</td>
+ <td><a name="tserver_session_update_idle_max" class="prop"></a> tserver.session.update.idle.max</td>
<td>When a tablet server’s SimpleTimer thread triggers to check idle sessions, this configurable option will be used to evaluate update sessions to determine if they can be closed due to inactivity<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1m</code></td>
</tr>
<tr>
- <td><a name="tserver_slow_flush_time"></a> tserver.slow.flush.time</td>
+ <td><a name="tserver_slow_flush_time" class="prop"></a> tserver.slow.flush.time</td>
<td>If a flush to the write-ahead log takes longer than this period of time, debugging information will written, and may result in a log rollover.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">100ms</code></td>
</tr>
<tr>
- <td><a name="tserver_sort_buffer_size"></a> tserver.sort.buffer.size</td>
+ <td><a name="tserver_sort_buffer_size" class="prop"></a> tserver.sort.buffer.size</td>
<td>The amount of memory to use when sorting logs during recovery.<br /><strong>type:</strong> MEMORY, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10%</code></td>
</tr>
<tr>
- <td><a name="tserver_summary_partition_threads"></a> tserver.summary.partition.threads</td>
+ <td><a name="tserver_summary_partition_threads" class="prop"></a> tserver.summary.partition.threads</td>
<td>Summary data must be retrieved from files. For a large number of files, the files are broken into partitions of 100K files. This setting determines how many of these groups of 100K files will be processed concurrently.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10</code></td>
</tr>
<tr>
- <td><a name="tserver_summary_remote_threads"></a> tserver.summary.remote.threads</td>
+ <td><a name="tserver_summary_remote_threads" class="prop"></a> tserver.summary.remote.threads</td>
<td>For a partitioned group of 100K files, those files are grouped by tablet server. Then a remote tablet server is asked to gather summary data. This setting determines how many concurrent request are made per partition.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">128</code></td>
</tr>
<tr>
- <td><a name="tserver_summary_retrieval_threads"></a> tserver.summary.retrieval.threads</td>
+ <td><a name="tserver_summary_retrieval_threads" class="prop"></a> tserver.summary.retrieval.threads</td>
<td>The number of threads on each tablet server available to retrieve summary data, that is not currently in cache, from RFiles.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">10</code></td>
</tr>
<tr>
- <td><a name="tserver_tablet_split_midpoint_files_max"></a> tserver.tablet.split.midpoint.files.max</td>
+ <td><a name="tserver_tablet_split_midpoint_files_max" class="prop"></a> tserver.tablet.split.midpoint.files.max</td>
<td>To find a tablets split points, all index files are opened. This setting determines how many index files can be opened at once. When there are more index files than this setting multiple passes must be made, which is slower. However opening too many files at once can cause problems.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">300</code></td>
</tr>
<tr>
- <td><a name="tserver_total_mutation_queue_max"></a> tserver.total.mutation.queue.max</td>
+ <td><a name="tserver_total_mutation_queue_max" class="prop"></a> tserver.total.mutation.queue.max</td>
<td>The amount of memory used to store write-ahead-log mutations before flushing them.<br /><strong>type:</strong> MEMORY, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5%</code></td>
</tr>
<tr>
- <td><a name="tserver_wal_blocksize"></a> tserver.wal.blocksize</td>
+ <td><a name="tserver_wal_blocksize" class="prop"></a> tserver.wal.blocksize</td>
<td>The size of the HDFS blocks used to write to the Write-Ahead log. If zero, it will be 110% of tserver.walog.max.size (that is, try to use just one block)<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0</code></td>
</tr>
<tr>
- <td><a name="tserver_wal_replication"></a> tserver.wal.replication</td>
+ <td><a name="tserver_wal_replication" class="prop"></a> tserver.wal.replication</td>
<td>The replication to use when writing the Write-Ahead log to HDFS. If zero, it will use the HDFS default replication setting.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">0</code></td>
</tr>
<tr>
- <td><a name="tserver_wal_sync"></a> tserver.wal.sync</td>
+ <td><a name="tserver_wal_sync" class="prop"></a> tserver.wal.sync</td>
<td>Use the SYNC_BLOCK create flag to sync WAL writes to disk. Prevents problems recovering from sudden system resets.<br /><strong>type:</strong> BOOLEAN, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">true</code></td>
</tr>
<tr>
- <td><a name="tserver_wal_sync_method"></a> tserver.wal.sync.method</td>
+ <td><a name="tserver_wal_sync_method" class="prop"></a> tserver.wal.sync.method</td>
<td><strong>Deprecated.</strong> <del>This property is deprecated. Use table.durability instead.</del><br /><del><strong>type:</strong> STRING</del>, <del><strong>zk mutable:</strong> yes</del>, <del><strong>default value:</strong> <code class="highlighter-rouge">hsync</code></del></td>
</tr>
<tr>
- <td><a name="tserver_walog_max_age"></a> tserver.walog.max.age</td>
+ <td><a name="tserver_walog_max_age" class="prop"></a> tserver.walog.max.age</td>
<td>The maximum age for each write-ahead log.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">24h</code></td>
</tr>
<tr>
- <td><a name="tserver_walog_max_size"></a> tserver.walog.max.size</td>
+ <td><a name="tserver_walog_max_size" class="prop"></a> tserver.walog.max.size</td>
<td>The maximum size for each write-ahead log. See comment for property tserver.memory.maps.max<br /><strong>type:</strong> BYTES, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1g</code></td>
</tr>
<tr>
- <td><a name="tserver_walog_maximum_wait_duration"></a> tserver.walog.maximum.wait.duration</td>
+ <td><a name="tserver_walog_maximum_wait_duration" class="prop"></a> tserver.walog.maximum.wait.duration</td>
<td>The maximum amount of time to wait after a failure to create a WAL file.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">5m</code></td>
</tr>
<tr>
- <td><a name="tserver_walog_tolerated_creation_failures"></a> tserver.walog.tolerated.creation.failures</td>
+ <td><a name="tserver_walog_tolerated_creation_failures" class="prop"></a> tserver.walog.tolerated.creation.failures</td>
<td>The maximum number of failures tolerated when creating a new WAL file within the period specified by tserver.walog.failures.period. Exceeding this number of failures in the period causes the TabletServer to exit.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">50</code></td>
</tr>
<tr>
- <td><a name="tserver_walog_tolerated_wait_increment"></a> tserver.walog.tolerated.wait.increment</td>
+ <td><a name="tserver_walog_tolerated_wait_increment" class="prop"></a> tserver.walog.tolerated.wait.increment</td>
<td>The amount of time to wait between failures to create a WALog.<br /><strong>type:</strong> TIMEDURATION, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">1000ms</code></td>
</tr>
<tr>
- <td><a name="tserver_workq_threads"></a> tserver.workq.threads</td>
+ <td><a name="tserver_workq_threads" class="prop"></a> tserver.workq.threads</td>
<td>The number of threads for the distributed work queue. These threads are used for copying failed bulk files.<br /><strong>type:</strong> COUNT, <strong>zk mutable:</strong> yes, <strong>default value:</strong> <code class="highlighter-rouge">2</code></td>
</tr>
</tbody>
@@ -1361,7 +1369,7 @@
<div class="row" style="margin-top: 20px;">
<div class="col-md-10"><strong>Find documentation for all releases in the <a href="/docs-archive">archive</strong></div>
- <div class="col-md-2"><a class="pull-right" href="https://github.com/apache/accumulo-website/edit/master/_docs-2-0/administration/configuration-properties.md" role="button"><i class="glyphicon glyphicon-pencil"></i> <small>Edit this page</small></a></div>
+ <div class="col-md-2"><a class="pull-right" href="https://github.com/apache/accumulo-website/edit/master/_docs-2-0/administration/properties.md" role="button"><i class="glyphicon glyphicon-pencil"></i> <small>Edit this page</small></a></div>
</div>
</div>
</div>
diff --git a/docs/2.0/administration/replication.html b/docs/2.0/administration/replication.html
index 60bec1d..95c622e 100644
--- a/docs/2.0/administration/replication.html
+++ b/docs/2.0/administration/replication.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/administration/ssl.html b/docs/2.0/administration/ssl.html
index 31b7833..42aa313 100644
--- a/docs/2.0/administration/ssl.html
+++ b/docs/2.0/administration/ssl.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
@@ -361,11 +361,11 @@ these files already exist.</p>
<p>In <code class="highlighter-rouge">accumulo-site.xml</code>, the following properties are required:</p>
<ul>
- <li><strong>rpc.javax.net.ssl.keyStore</strong>=<em>The path on the local filesystem to the keystore containing the server’s certificate</em></li>
- <li><strong>rpc.javax.net.ssl.keyStorePassword</strong>=<em>The password for the keystore containing the server’s certificate</em></li>
- <li><strong>rpc.javax.net.ssl.trustStore</strong>=<em>The path on the local filesystem to the keystore containing the certificate authority’s public key</em></li>
- <li><strong>rpc.javax.net.ssl.trustStorePassword</strong>=<em>The password for the keystore containing the certificate authority’s public key</em></li>
- <li><strong>instance.rpc.ssl.enabled</strong>=<em>true</em></li>
+ <li><a href="/docs/2.0/administration/properties#rpc_javax_net_ssl_keyStore">rpc.javax.net.ssl.keyStore</a> = <em>The path on the local filesystem to the keystore containing the server’s certificate</em></li>
+ <li><a href="/docs/2.0/administration/properties#rpc_javax_net_ssl_keyStorePassword">rpc.javax.net.ssl.keyStorePassword</a> = <em>The password for the keystore containing the server’s certificate</em></li>
+ <li><a href="/docs/2.0/administration/properties#rpc_javax_net_ssl_trustStore">rpc.javax.net.ssl.trustStore</a> = <em>The path on the local filesystem to the keystore containing the certificate authority’s public key</em></li>
+ <li><a href="/docs/2.0/administration/properties#rpc_javax_net_ssl_trustStorePassword">rpc.javax.net.ssl.trustStorePassword</a> = <em>The password for the keystore containing the certificate authority’s public key</em></li>
+ <li><a href="/docs/2.0/administration/properties#instance_rpc_ssl_enabled">instance.rpc.ssl.enabled</a> = <em>true</em></li>
</ul>
<p>Optionally, SSL client-authentication (two-way SSL) can also be enabled by setting
@@ -383,18 +383,18 @@ the client configuration file whose default location is <code class="highlighter
<p>The following properties must be set to connect to an Accumulo instance using SSL:</p>
<ul>
- <li><strong>rpc.javax.net.ssl.trustStore</strong>=<em>The path on the local filesystem to the keystore containing the certificate authority’s public key</em></li>
- <li><strong>rpc.javax.net.ssl.trustStorePassword</strong>=<em>The password for the keystore containing the certificate authority’s public key</em></li>
- <li><strong>instance.rpc.ssl.enabled</strong>=<em>true</em></li>
+ <li><a href="/docs/2.0/administration/properties#rpc_javax_net_ssl_trustStore">rpc.javax.net.ssl.trustStore</a> = <em>The path on the local filesystem to the keystore containing the certificate authority’s public key</em></li>
+ <li><a href="/docs/2.0/administration/properties#rpc_javax_net_ssl_trustStorePassword">rpc.javax.net.ssl.trustStorePassword</a> = <em>The password for the keystore containing the certificate authority’s public key</em></li>
+ <li><a href="/docs/2.0/administration/properties#instance_rpc_ssl_enabled">instance.rpc.ssl.enabled</a> = <em>true</em></li>
</ul>
<p>If two-way SSL if enabled (<code class="highlighter-rouge">instance.rpc.ssl.clientAuth=true</code>) for the instance, the client must also define
their own certificate and enable client authenticate as well.</p>
<ul>
- <li><strong>rpc.javax.net.ssl.keyStore</strong>=<em>The path on the local filesystem to the keystore containing the server’s certificate</em></li>
- <li><strong>rpc.javax.net.ssl.keyStorePassword</strong>=<em>The password for the keystore containing the server’s certificate</em></li>
- <li><strong>instance.rpc.ssl.clientAuth</strong>=<em>true</em></li>
+ <li><a href="/docs/2.0/administration/properties#rpc_javax_net_ssl_keyStore">rpc.javax.net.ssl.keyStore</a> =<em>The path on the local filesystem to the keystore containing the server’s certificate</em></li>
+ <li><a href="/docs/2.0/administration/properties#rpc_javax_net_ssl_keyStorePassword">rpc.javax.net.ssl.keyStorePassword</a> = <em>The password for the keystore containing the server’s certificate</em></li>
+ <li><a href="/docs/2.0/administration/properties#instance_rpc_ssl_clientAuth">instance.rpc.ssl.clientAuth</a> = <em>true</em></li>
</ul>
<h2 id="generating-ssl-material-using-openssl">Generating SSL material using OpenSSL</h2>
@@ -458,6 +458,7 @@ keytool -import -trustcacerts -alias server-crt -file server.crt -keystore serve
methods are equivalent whether the certificate is generate for an Accumulo server or a client.</p>
+
<div class="row" style="margin-top: 20px;">
<div class="col-md-10"><strong>Find documentation for all releases in the <a href="/docs-archive">archive</strong></div>
<div class="col-md-2"><a class="pull-right" href="https://github.com/apache/accumulo-website/edit/master/_docs-2-0/administration/ssl.md" role="button"><i class="glyphicon glyphicon-pencil"></i> <small>Edit this page</small></a></div>
diff --git a/docs/2.0/administration/tracing.html b/docs/2.0/administration/tracing.html
index 01e99bc..5ef67f2 100644
--- a/docs/2.0/administration/tracing.html
+++ b/docs/2.0/administration/tracing.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
@@ -358,18 +358,18 @@ configure your server in <code class="highlighter-rouge">conf/tracers</code>. Th
user that the tracer connects to Accumulo with can be configured with the following properties (see the <a href="/docs/2.0/administration/configuration-management">configuration management</a>
page for setting Accumulo server properties)</p>
-<div class="highlighter-rouge"><pre class="highlight"><code>trace.user
-trace.token.property.password
-</code></pre>
-</div>
+<ul>
+ <li><a href="/docs/2.0/administration/properties#trace_user">trace.user</a></li>
+ <li><a href="/docs/2.0/administration/properties#trace_token_property_password">trace.token.property.password</a></li>
+</ul>
<p>Other tracer configuration properties include</p>
-<div class="highlighter-rouge"><pre class="highlight"><code>trace.port.client - port tracer listens on
-trace.table - table tracer writes to
-trace.zookeeper.path - zookeeper path where tracers register
-</code></pre>
-</div>
+<ul>
+ <li><a href="/docs/2.0/administration/properties#trace_port_client">trace.port.client</a> - port tracer listens on</li>
+ <li><a href="/docs/2.0/administration/properties#trace_table">trace.table</a> - table tracer writes to</li>
+ <li><a href="/docs/2.0/administration/properties#trace_zookeeper_path">trace.zookeeper.path</a> - zookeeper path where tracers register</li>
+</ul>
<p>The zookeeper path is configured to /tracers by default. If
multiple Accumulo instances are sharing the same ZooKeeper
@@ -383,14 +383,10 @@ configured is org.apache.accumulo.core.trace.ZooTraceClient, which
sends spans to an Accumulo Tracer process, as discussed in the
previous section. This default can be changed to a different span
receiver, or additional span receivers can be added in a
-comma-separated list, by modifying the property</p>
-
-<div class="highlighter-rouge"><pre class="highlight"><code>trace.span.receivers
-</code></pre>
-</div>
+comma-separated list, by modifying the property <a href="/docs/2.0/administration/properties#trace_span_receivers">trace.span.receivers</a>.</p>
<p>Individual span receivers may require their own configuration
-parameters, which are grouped under the trace.span.receiver.*
+parameters, which are grouped under the <a href="/docs/2.0/administration/properties#trace_span_receiver_prefix">trace.span.receiver.*</a>
prefix. ZooTraceClient uses the following properties. The first
three properties are populated from other Accumulo properties,
while the remaining ones should be prefixed with
@@ -407,13 +403,13 @@ tracer.span.min.ms - minimum span length to store (in ms, default 1)
<p>Note that to configure an Accumulo client for tracing, including
the Accumulo shell, the client configuration must be given the same
-trace.span.receivers, trace.span.receiver.*, and trace.zookeeper.path
+<a href="/docs/2.0/administration/properties#trace_span_receivers">trace.span.receivers</a>, <a href="/docs/2.0/administration/properties#trace_span_receiver_prefix">trace.span.receiver.*</a>, and <a href="/docs/2.0/administration/properties#trace_zookeeper_path">trace.zookeeper.path</a>
properties as the servers have.</p>
<p>Hadoop can also be configured to send traces to Accumulo, as of
Hadoop 2.6.0, by setting properties in Hadoop’s core-site.xml
-file. Instead of using the trace.span.receiver.* prefix, Hadoop
-uses hadoop.htrace.*. The Hadoop configuration does not have
+file. Instead of using the [trace.span.receiver.<em>] prefix, Hadoop
+uses hadoop.htrace.</em>. The Hadoop configuration does not have
access to Accumulo’s properties, so the
hadoop.htrace.tracer.zookeeper.host property must be specified.
The zookeeper timeout defaults to 30000 (30 seconds), and the
diff --git a/docs/2.0/administration/upgrading.html b/docs/2.0/administration/upgrading.html
index e7b122e..8ad278d 100644
--- a/docs/2.0/administration/upgrading.html
+++ b/docs/2.0/administration/upgrading.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/development/development_tools.html b/docs/2.0/development/development_tools.html
index f3195fa..da4210c 100644
--- a/docs/2.0/development/development_tools.html
+++ b/docs/2.0/development/development_tools.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/development/high_speed_ingest.html b/docs/2.0/development/high_speed_ingest.html
index 36207f1..e28a4f6 100644
--- a/docs/2.0/development/high_speed_ingest.html
+++ b/docs/2.0/development/high_speed_ingest.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/development/iterators.html b/docs/2.0/development/iterators.html
index 587e9b2..27f700a 100644
--- a/docs/2.0/development/iterators.html
+++ b/docs/2.0/development/iterators.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/development/mapreduce.html b/docs/2.0/development/mapreduce.html
index 04f3038..1706a8d 100644
--- a/docs/2.0/development/mapreduce.html
+++ b/docs/2.0/development/mapreduce.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/development/proxy.html b/docs/2.0/development/proxy.html
index d22fa62..7165e20 100644
--- a/docs/2.0/development/proxy.html
+++ b/docs/2.0/development/proxy.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/development/sampling.html b/docs/2.0/development/sampling.html
index 2e99cd1..ce9d9c1 100644
--- a/docs/2.0/development/sampling.html
+++ b/docs/2.0/development/sampling.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/development/security.html b/docs/2.0/development/security.html
index 64cacad..b4bbfe3 100644
--- a/docs/2.0/development/security.html
+++ b/docs/2.0/development/security.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/development/summaries.html b/docs/2.0/development/summaries.html
index 6661861..b28ced3 100644
--- a/docs/2.0/development/summaries.html
+++ b/docs/2.0/development/summaries.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
@@ -377,12 +377,12 @@ information.</p>
<p>The following tablet server and table properties configure summarization.</p>
<ul>
- <li><a href="/docs/2.0/administration/configuration-properties#tserver_cache_summary_size">tserver.cache.summary.size</a></li>
- <li><a href="/docs/2.0/administration/configuration-properties#tserver_summary_partition_threads">tserver.summary.partition.threads</a></li>
- <li><a href="/docs/2.0/administration/configuration-properties#tserver_summary_remote_threads">tserver.summary.remote.threads</a></li>
- <li><a href="/docs/2.0/administration/configuration-properties#tserver_summary_retreival_threads">tserver.summary.retrieval.threads</a></li>
- <li><a href="/docs/2.0/administration/configuration-properties#table_summarizer_prefix">table.summarizer.*</a></li>
- <li><a href="/docs/2.0/administration/configuration-properties#table_file_summary_maxSize">table.file.summary.maxSize</a></li>
+ <li><a href="/docs/2.0/administration/properties#tserver_cache_summary_size">tserver.cache.summary.size</a></li>
+ <li><a href="/docs/2.0/administration/properties#tserver_summary_partition_threads">tserver.summary.partition.threads</a></li>
+ <li><a href="/docs/2.0/administration/properties#tserver_summary_remote_threads">tserver.summary.remote.threads</a></li>
+ <li><a href="/docs/2.0/administration/properties#tserver_summary_retreival_threads">tserver.summary.retrieval.threads</a></li>
+ <li><a href="/docs/2.0/administration/properties#table_summarizer_prefix">table.summarizer.*</a></li>
+ <li><a href="/docs/2.0/administration/properties#table_file_summary_maxSize">table.file.summary.maxSize</a></li>
</ul>
<h2 id="permissions">Permissions</h2>
diff --git a/docs/2.0/getting-started/clients.html b/docs/2.0/getting-started/clients.html
index 76961ff..561debd 100644
--- a/docs/2.0/getting-started/clients.html
+++ b/docs/2.0/getting-started/clients.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/getting-started/design.html b/docs/2.0/getting-started/design.html
index 32f2e44..ad0a556 100644
--- a/docs/2.0/getting-started/design.html
+++ b/docs/2.0/getting-started/design.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/getting-started/quick-install.html b/docs/2.0/getting-started/quick-install.html
index a0f0d0e..0e9458c 100644
--- a/docs/2.0/getting-started/quick-install.html
+++ b/docs/2.0/getting-started/quick-install.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/getting-started/shell.html b/docs/2.0/getting-started/shell.html
index b982344..58e8f4c 100644
--- a/docs/2.0/getting-started/shell.html
+++ b/docs/2.0/getting-started/shell.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/getting-started/table_configuration.html b/docs/2.0/getting-started/table_configuration.html
index 66c68e8..781c1b5 100644
--- a/docs/2.0/getting-started/table_configuration.html
+++ b/docs/2.0/getting-started/table_configuration.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
@@ -335,7 +335,7 @@
<p>Accumulo tables have a few options that can be configured to alter the default
behavior of Accumulo as well as improve performance based on the data stored.
These include locality groups, constraints, bloom filters, iterators, and block
-cache. See the <a href="/docs/2.0/administration/configuration-properties">configuration properties documentation</a> for
+cache. See the <a href="/docs/2.0/administration/properties">configuration properties documentation</a> for
a complete list of available configuration options.</p>
<h2 id="locality-groups">Locality Groups</h2>
@@ -783,7 +783,7 @@ compact tablets that overlap the given row range.</p>
<h3 id="compaction-strategies">Compaction Strategies</h3>
<p>The default behavior of major compactions is defined in the class DefaultCompactionStrategy.
-This behavior can be changed by overriding <a href="/docs/2.0/administration/configuration-properties#table_majc_compaction_strategy">table.majc.compaction.strategy</a> with a fully
+This behavior can be changed by overriding <a href="/docs/2.0/administration/properties#table_majc_compaction_strategy">table.majc.compaction.strategy</a> with a fully
qualified class name.</p>
<p>Custom compaction strategies can have additional properties that are specified following the prefix property:</p>
diff --git a/docs/2.0/getting-started/table_design.html b/docs/2.0/getting-started/table_design.html
index 5af560a..d21ab64 100644
--- a/docs/2.0/getting-started/table_design.html
+++ b/docs/2.0/getting-started/table_design.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/troubleshooting/advanced.html b/docs/2.0/troubleshooting/advanced.html
index 9fb6981..db9bfb1 100644
--- a/docs/2.0/troubleshooting/advanced.html
+++ b/docs/2.0/troubleshooting/advanced.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/troubleshooting/basic.html b/docs/2.0/troubleshooting/basic.html
index 271a615..d273bf0 100644
--- a/docs/2.0/troubleshooting/basic.html
+++ b/docs/2.0/troubleshooting/basic.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/troubleshooting/system-metadata-tables.html b/docs/2.0/troubleshooting/system-metadata-tables.html
index 73544bf..1c645de 100644
--- a/docs/2.0/troubleshooting/system-metadata-tables.html
+++ b/docs/2.0/troubleshooting/system-metadata-tables.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/docs/2.0/troubleshooting/tools.html b/docs/2.0/troubleshooting/tools.html
index 20021e6..2dacdb7 100644
--- a/docs/2.0/troubleshooting/tools.html
+++ b/docs/2.0/troubleshooting/tools.html
@@ -250,7 +250,7 @@
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-management">Configuration Management</a></div>
- <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/configuration-properties">Configuration Properties</a></div>
+ <div class="row doc-sidebar-link"><a href="/docs/2.0/administration/properties">Configuration Properties</a></div>
<div class="row doc-sidebar-link"><a href="/docs/2.0/administration/monitoring-metrics">Monitoring & Metrics</a></div>
diff --git a/feed.xml b/feed.xml
index 7b82a5a..cf3ea11 100644
--- a/feed.xml
+++ b/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, 06 Dec 2017 17:54:30 -0500</pubDate>
- <lastBuildDate>Wed, 06 Dec 2017 17:54:30 -0500</lastBuildDate>
+ <pubDate>Thu, 07 Dec 2017 16:53:14 -0500</pubDate>
+ <lastBuildDate>Thu, 07 Dec 2017 16:53:14 -0500</lastBuildDate>
<generator>Jekyll v3.5.2</generator>
--
To stop receiving notification emails like this one, please contact
['"commits@accumulo.apache.org" <co...@accumulo.apache.org>'].