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/12 20:59:17 UTC
[accumulo-website] branch asf-site updated: Jekyll build from
master:912db32
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 d3a34fe Jekyll build from master:912db32
d3a34fe is described below
commit d3a34fea77c60555aa3bff6f1b89a1acad4049e7
Author: Mike Walch <mw...@apache.org>
AuthorDate: Tue Dec 12 15:56:20 2017 -0500
Jekyll build from master:912db32
Made properties linkable in table configuration (#52)
---
docs/2.0/getting-started/table_configuration.html | 75 ++++++++---------------
feed.xml | 4 +-
2 files changed, 29 insertions(+), 50 deletions(-)
diff --git a/docs/2.0/getting-started/table_configuration.html b/docs/2.0/getting-started/table_configuration.html
index 168fe13..e099e22 100644
--- a/docs/2.0/getting-started/table_configuration.html
+++ b/docs/2.0/getting-started/table_configuration.html
@@ -389,15 +389,8 @@ user@myinstance mytable> getgroups -t mytable
<p>The assignment of Column Families to Locality Groups can be changed at any time. The
physical movement of column families into their new locality groups takes place via
-the periodic Major Compaction process that takes place continuously in the
-background. Major Compaction can also be scheduled to take place immediately
-through the shell:</p>
-
-<div class="highlighter-rouge"><pre class="highlight"><code>user@myinstance mytable> compact -t mytable
-</code></pre>
-</div>
-
-<p>If needed, the compaction can be canceled using <code class="highlighter-rouge">compact --cancel -t mytable</code>.</p>
+the periodic <a href="#compaction">major compaction</a> process that takes place continuously in the
+background or manually using the <code class="highlighter-rouge">compact</code> command in the shell.</p>
<h2 id="constraints">Constraints</h2>
@@ -432,9 +425,8 @@ change to an existing constraint class requires Accumulo to be restarted.</p>
<p>As mutations are applied to an Accumulo table, several files are created per tablet. If
bloom filters are enabled, Accumulo will create and load a small data structure into
memory to determine whether a file contains a given key before opening the file.
-This can speed up lookups considerably.</p>
-
-<p>To enable bloom filters, enter the following command in the Shell:</p>
+This can speed up lookups considerably. Bloom filters can be enabled on a table by
+setting the <a href="/docs/2.0/administration/properties#table_bloom_enabled">table.bloom.enabled</a> property to <code class="highlighter-rouge">true</code> in the shell:</p>
<div class="highlighter-rouge"><pre class="highlight"><code>user@myinstance> config -t mytable -s table.bloom.enabled=true
</code></pre>
@@ -702,11 +694,7 @@ added to tablets directly by bulk import. In the background tablet servers run
major compactions to merge multiple files into one. The tablet server has to
decide which tablets to compact and which files within a tablet to compact.
This decision is made using the compaction ratio, which is configurable on a
-per table basis. To configure this ratio modify the following property:</p>
-
-<div class="highlighter-rouge"><pre class="highlight"><code>table.compaction.major.ratio
-</code></pre>
-</div>
+per table basis by the <a href="/docs/2.0/administration/properties#table_compaction_major_ratio">table.compaction.major.ratio</a> property.</p>
<p>Increasing this ratio will result in more files per tablet and less compaction
work. More files per tablet means more higher query latency. So adjusting
@@ -720,21 +708,11 @@ files in a tablet, the largest file is removed from consideration, and the
remaining files are considered for compaction. This is repeated until a
compaction is triggered or there are no files left to consider.</p>
-<p>The number of background threads tablet servers use to run major compactions is
-configurable. To configure this modify the following property:</p>
-
-<div class="highlighter-rouge"><pre class="highlight"><code>tserver.compaction.major.concurrent.max
-</code></pre>
-</div>
-
-<p>Also, the number of threads tablet servers use for minor compactions is
-configurable. To configure this modify the following property:</p>
+<p>The number of background threads tablet servers use to run major and minor
+compactions is configured by the <a href="/docs/2.0/administration/properties#tserver_compaction_major_concurrent_max">tserver.compaction.major.concurrent.max</a>
+and <a href="/docs/2.0/administration/properties#tserver_compaction_minor_concurrent_max">tserver.compaction.minor.concurrent.max</a> properties respectively.</p>
-<div class="highlighter-rouge"><pre class="highlight"><code>tserver.compaction.minor.concurrent.max
-</code></pre>
-</div>
-
-<p>The numbers of minor and major compactions running and queued is visible on the
+<p>The numbers of major and minor compactions running and queued is visible on the
Accumulo monitor page. This allows you to see if compactions are backing up
and adjustments to the above settings are needed. When adjusting the number of
threads available for compactions, consider the number of cores and other tasks
@@ -754,15 +732,9 @@ alleviate backups by lowering the amount of major compaction work that needs to
be done.</p>
<p>Another option to deal with the files per tablet growing too large is to adjust
-the following property:</p>
-
-<div class="highlighter-rouge"><pre class="highlight"><code>table.file.max
-</code></pre>
-</div>
-
-<p>When a tablet reaches this number of files and needs to flush its in-memory
-data to disk, it will choose to do a merging minor compaction. A merging minor
-compaction will merge the tablet’s smallest file with the data in memory at
+the <a href="/docs/2.0/administration/properties#table_file_max">table.file.max</a> property. When a tablet reaches this number of files and needs
+to flush its in-memory data to disk, it will choose to do a merging minor compaction.
+A merging minor compaction will merge the tablet’s smallest file with the data in memory at
minor compaction time. Therefore the number of files will not grow beyond this
limit. This will make minor compactions take longer, which will cause ingest
performance to decrease. This can cause ingest to slow down until major
@@ -776,13 +748,20 @@ The amount of work done by major compactions is O(N*log<sub>R</sub>(N)) where
R is the compaction ratio.</p>
<p>Compactions can be initiated manually for a table. To initiate a minor
-compaction, use the flush command in the shell. To initiate a major compaction,
-use the compact command in the shell. The compact command will compact all
-tablets in a table to one file. Even tablets with one file are compacted. This
-is useful for the case where a major compaction filter is configured for a
-table. In 1.4 the ability to compact a range of a table was added. To use this
-feature specify start and stop rows for the compact command. This will only
-compact tablets that overlap the given row range.</p>
+compaction, use the <code class="highlighter-rouge">flush</code> command in the shell. To initiate a major compaction,
+use the <code class="highlighter-rouge">compact</code> command in the shell:</p>
+
+<div class="highlighter-rouge"><pre class="highlight"><code>user@myinstance mytable> compact -t mytable
+</code></pre>
+</div>
+
+<p>If needed, the compaction can be canceled using <code class="highlighter-rouge">compact --cancel -t mytable</code>.</p>
+
+<p>The <code class="highlighter-rouge">compact</code> command will compact all tablets in a table to one file. Even tablets
+with one file are compacted. This is useful for the case where a major compaction
+filter is configured for a table. In 1.4, the ability to compact a range of a table
+was added. To use this feature specify start and stop rows for the compact command.
+This will only compact tablets that overlap the given row range.</p>
<h3 id="compaction-strategies">Compaction Strategies</h3>
@@ -804,7 +783,7 @@ property <code class="highlighter-rouge">table.majc.compaction.strategy.opts.siz
<p><code class="highlighter-rouge">TwoTierCompactionStrategy</code> is a hybrid compaction strategy that supports two types of compression. If the total size of
files being compacted is larger than <code class="highlighter-rouge">table.majc.compaction.strategy.opts.file.large.compress.threshold</code> than a larger
compression type will be used. The larger compression type is specified in <code class="highlighter-rouge">table.majc.compaction.strategy.opts.file.large.compress.type</code>.
-Otherwise, the configured table compression will be used. To use this strategy with minor compactions set <code class="highlighter-rouge">table.file.compress.type=snappy</code>
+Otherwise, the configured table compression will be used. To use this strategy with minor compactions set <a href="/docs/2.0/administration/properties#table_file_compress_type">table.file.compress.type</a> to <code class="highlighter-rouge">snappy</code>
and set a different compress type in <code class="highlighter-rouge">table.majc.compaction.strategy.opts.file.large.compress.type</code> for larger files.</p>
<h2 id="pre-splitting-tables">Pre-splitting tables</h2>
diff --git a/feed.xml b/feed.xml
index e3e6a75..d13695d 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>Tue, 12 Dec 2017 12:13:29 -0500</pubDate>
- <lastBuildDate>Tue, 12 Dec 2017 12:13:29 -0500</lastBuildDate>
+ <pubDate>Tue, 12 Dec 2017 15:56:06 -0500</pubDate>
+ <lastBuildDate>Tue, 12 Dec 2017 15:56:06 -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>'].