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/11/03 16:53:52 UTC
[accumulo-website] branch asf-site updated: Jekyll build from
master:cba2cca
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 28eaa9e Jekyll build from master:cba2cca
28eaa9e is described below
commit 28eaa9e754128b67ed1011777f08cbcb0c2ec552
Author: Mike Walch <mw...@apache.org>
AuthorDate: Fri Nov 3 12:39:38 2017 -0400
Jekyll build from master:cba2cca
ACCUMULO-4735 Fixed typos and spelling errors (#34)
---
blog/2014/05/03/accumulo-classloader.html | 2 +-
blog/2016/11/16/simpler-scripts-and-config.html | 6 +++---
blog/2017/03/06/security-performance-implications.html | 2 +-
blog/2017/04/21/introducing-uno-and-muchos.html | 4 ++--
contributor/git.html | 2 +-
contributor/making-release.html | 2 +-
contributor/verifying-release.html | 4 ++--
docs/2.0/administration/configuration-management.html | 2 +-
docs/2.0/administration/in-depth-install.html | 12 ++++++------
docs/2.0/administration/kerberos.html | 8 ++++----
docs/2.0/administration/replication.html | 4 ++--
docs/2.0/administration/ssl.html | 4 ++--
docs/2.0/development/development_tools.html | 2 +-
docs/2.0/development/iterators.html | 8 ++++----
docs/2.0/development/proxy.html | 2 +-
docs/2.0/development/security.html | 2 +-
docs/2.0/getting-started/quick-install.html | 4 ++--
docs/2.0/getting-started/shell.html | 2 +-
docs/2.0/getting-started/table_design.html | 2 +-
docs/2.0/troubleshooting/advanced.html | 10 +++++-----
feed.xml | 18 +++++++++---------
release/accumulo-1.5.1/index.html | 2 +-
release/accumulo-1.5.2/index.html | 2 +-
release/accumulo-1.6.0/index.html | 2 +-
release/accumulo-1.6.1/index.html | 2 +-
release/accumulo-1.6.6/index.html | 4 ++--
release/accumulo-1.7.0/index.html | 2 +-
release/accumulo-1.7.2/index.html | 4 ++--
release/accumulo-1.8.0/index.html | 6 +++---
release/accumulo-1.8.1/index.html | 2 +-
30 files changed, 64 insertions(+), 64 deletions(-)
diff --git a/blog/2014/05/03/accumulo-classloader.html b/blog/2014/05/03/accumulo-classloader.html
index 3c3be46..c8d7720 100644
--- a/blog/2014/05/03/accumulo-classloader.html
+++ b/blog/2014/05/03/accumulo-classloader.html
@@ -204,7 +204,7 @@
</code></pre>
</div>
-<p>Context classloaders do not have to be defined in the accumulo-site.xml file. The “general.vfs.context.classpath.{context}” property can be defined on the table either programatically or manually in the shell. Then set the “table.classpath.context” property on your table.</p>
+<p>Context classloaders do not have to be defined in the accumulo-site.xml file. The “general.vfs.context.classpath.{context}” property can be defined on the table either programmatically or manually in the shell. Then set the “table.classpath.context” property on your table.</p>
<h3 id="known-issues">Known Issues</h3>
diff --git a/blog/2016/11/16/simpler-scripts-and-config.html b/blog/2016/11/16/simpler-scripts-and-config.html
index dc35f5f..b3fcb33 100644
--- a/blog/2016/11/16/simpler-scripts-and-config.html
+++ b/blog/2016/11/16/simpler-scripts-and-config.html
@@ -172,9 +172,9 @@ bootstrap_hdfs.sh config.sh start-daemon.sh s
</div>
<p>The number of scripts made it difficult to know which scripts to use. If you added the <code class="highlighter-rouge">bin/</code> directory to your
-<code class="highlighter-rouge">PATH</code>, it could add unecessary commands to your PATH or cause commands to be overriden due generic names
+<code class="highlighter-rouge">PATH</code>, it could add unnecessary commands to your PATH or cause commands to be overridden due generic names
(like ‘start-all.sh’). The number of scripts were reduced by removing scripts that are no longer used and combining
-scripts with similiar functionality.</p>
+scripts with similar functionality.</p>
<p>Starting with 2.0.0, Accumulo will only have 4 scripts in its <code class="highlighter-rouge">bin/</code> directory:</p>
@@ -281,7 +281,7 @@ Services:
monitor Accumulo monitor
master Accumulo master
tserver Accumulo tserver
- tracer Accumulo tracter
+ tracer Accumulo tracer
Commands:
start Starts service
diff --git a/blog/2017/03/06/security-performance-implications.html b/blog/2017/03/06/security-performance-implications.html
index c575897..3498fdc 100644
--- a/blog/2017/03/06/security-performance-implications.html
+++ b/blog/2017/03/06/security-performance-implications.html
@@ -405,7 +405,7 @@ in the output generated by <a href="https://github.com/apache/accumulo/blob/1.7/
<p><a href="/images/blog/201702_security/accumuloFiles.png"><img src="/images/blog/201702_security/accumuloFiles.png" alt="" width="800px" /></a></p>
<p>As can be seen in the plots above, the different security settings have
-relatively consistent, discernable median run characteristics. The big
+relatively consistent, discernible median run characteristics. The big
dip in each TOTAL_INGEST coincides with a large number of major
compactions, a rate decrease for TABLE_RECS, and a decrease in
AVG_FILES/TABLET.</p>
diff --git a/blog/2017/04/21/introducing-uno-and-muchos.html b/blog/2017/04/21/introducing-uno-and-muchos.html
index 86a9c47..a46f745 100644
--- a/blog/2017/04/21/introducing-uno-and-muchos.html
+++ b/blog/2017/04/21/introducing-uno-and-muchos.html
@@ -240,8 +240,8 @@ vim conf/muchos.props
<h2 id="conclusion">Conclusion</h2>
-<p>Uno and Muchos automate installing Accumulo for developmment and testing. While not recommended for production
-use at this time, Muchos is a great reference for running Accumulo in production. System admistrators can
+<p>Uno and Muchos automate installing Accumulo for development and testing. While not recommended for production
+use at this time, Muchos is a great reference for running Accumulo in production. System administrators can
reference the <a href="https://www.ansible.com/">Ansible</a> code in Muchos to automate management of their own clusters.</p>
diff --git a/contributor/git.html b/contributor/git.html
index e742126..d414a51 100644
--- a/contributor/git.html
+++ b/contributor/git.html
@@ -452,7 +452,7 @@ with <code class="highlighter-rouge"><apache_id>/ACCUMULO-<issue#>[-
<p><code class="highlighter-rouge">git checkout <apache_id>/ACCUMULO-<issue#> master</code></p>
</li>
<li>
- <p>Create the feature, commiting early and often to appropriately outline the
+ <p>Create the feature, committing early and often to appropriately outline the
“story” behind the feature and it’s implementation.</p>
</li>
<li>
diff --git a/contributor/making-release.html b/contributor/making-release.html
index d149714..502e10e 100644
--- a/contributor/making-release.html
+++ b/contributor/making-release.html
@@ -187,7 +187,7 @@ the maven-release-plugin and staging the release candidate).</li>
<p>You should use the provided script assemble/build.sh to create the release candidate. This script is
desirable as it activates all necessary maven profiles in addition to verifying that certain preconditions
-are met, like RPM signing availablilty and the ability to sign files using GPG. The –test option can
+are met, like RPM signing availability and the ability to sign files using GPG. The –test option can
be used as a dry run for creating a release candidate. The –create-release-candidate option should be
used to create the actual release candidate.</p>
diff --git a/contributor/verifying-release.html b/contributor/verifying-release.html
index e41d868..ef47a64 100644
--- a/contributor/verifying-release.html
+++ b/contributor/verifying-release.html
@@ -177,7 +177,7 @@ trumps anything written here.</p>
property in the <code class="highlighter-rouge">pom.xml</code> and using the staging repo. Also, run the unit/integration tests using <code class="highlighter-rouge">mvn verify</code>.</p>
</li>
<li>
- <p>Run Accumulo’s distributed tests (i.e. random walk, continous ingest). These tests are intended to be run for days
+ <p>Run Accumulo’s distributed tests (i.e. random walk, continuous ingest). These tests are intended to be run for days
on end while injecting faults into the system. These are the tests that truly verify the correctness of Accumulo on
real systems. Starting with 2.0, these tests are run using the <a href="https://github.com/apache/accumulo-testing">Accumulo Testing repo</a>. See the <a href="https://github.com/apache/accumulo-testing/blob/master/README.md">README.md</a>
for more information. Before 2.0, these tests are found in Accumulo tarball at <code class="highlighter-rouge">test/system/randomwalk</code> and
@@ -196,7 +196,7 @@ release, the release should be vetoed via the normal voting process. New major r
<h3 id="stand-alone">Stand alone</h3>
-<p>The following steps can be taken without having an underlying cluster. They SHOULD be handled with each Hadoop profile available for a given release version. To activate an alternative profile specify e.g. “-Dhadoop.profile=2” for the Hadoop 2 profile on the Maven commandline. Some older versions of Accumulo referred to Hadoop profiles diferently; see the README that came with said versions for details on building against different Hadoop versions.</p>
+<p>The following steps can be taken without having an underlying cluster. They SHOULD be handled with each Hadoop profile available for a given release version. To activate an alternative profile specify e.g. “-Dhadoop.profile=2” for the Hadoop 2 profile on the Maven commandline. Some older versions of Accumulo referred to Hadoop profiles differently; see the README that came with said versions for details on building against different Hadoop versions.</p>
<ol>
<li>All JUnit tests must pass. This should be a requirement of any patch so it should never be an issue of the codebase.
diff --git a/docs/2.0/administration/configuration-management.html b/docs/2.0/administration/configuration-management.html
index 007153a..3660a8b 100644
--- a/docs/2.0/administration/configuration-management.html
+++ b/docs/2.0/administration/configuration-management.html
@@ -345,7 +345,7 @@
<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.
-While defalt values have the lowest precendence, they are usually optimal. However, there are cases where a change can increase query and ingest performance.</p>
+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>
diff --git a/docs/2.0/administration/in-depth-install.html b/docs/2.0/administration/in-depth-install.html
index 3a081bf..b17f9ca 100644
--- a/docs/2.0/administration/in-depth-install.html
+++ b/docs/2.0/administration/in-depth-install.html
@@ -827,7 +827,7 @@ take some time for particular configurations.</p>
server won’t start; at a minimum this needs to be on the host(s) being added,
but in practice it’s good to ensure consistent configuration across all nodes.</p>
-<h3 id="decomissioning-a-tablet-server">Decomissioning a Tablet Server</h3>
+<h3 id="decommissioning-a-tablet-server">Decommissioning a Tablet Server</h3>
<p>If you need to take a node out of operation, you can trigger a graceful shutdown of a tablet
server. Accumulo will automatically rebalance the tablets across the available tablet servers.</p>
@@ -931,12 +931,12 @@ that the only volume displayed is the volume from the current namenode’s HDFS
Listing volumes referenced in accumulo.root tablets section
Volume : hdfs://namenode.example.com:8020/accumulo
-Listing volumes referenced in accumulo.root deletes section (volume replacement occurrs at deletion time)
+Listing volumes referenced in accumulo.root deletes section (volume replacement occurs at deletion time)
Listing volumes referenced in accumulo.metadata tablets section
Volume : hdfs://namenode.example.com:8020/accumulo
-Listing volumes referenced in accumulo.metadata deletes section (volume replacement occurrs at deletion time)
+Listing volumes referenced in accumulo.metadata deletes section (volume replacement occurs at deletion time)
</code></pre>
</div>
@@ -970,12 +970,12 @@ new nameservice volume shows up with <code class="highlighter-rouge">accumulo ad
Listing volumes referenced in accumulo.root tablets section
Volume : hdfs://namenode.example.com:8020/accumulo
Volume : hdfs://nameservice1/accumulo
-Listing volumes referenced in accumulo.root deletes section (volume replacement occurrs at deletion time)
+Listing volumes referenced in accumulo.root deletes section (volume replacement occurs at deletion time)
Listing volumes referenced in accumulo.metadata tablets section
Volume : hdfs://namenode.example.com:8020/accumulo
Volume : hdfs://nameservice1/accumulo
-Listing volumes referenced in accumulo.metadata deletes section (volume replacement occurrs at deletion time)
+Listing volumes referenced in accumulo.metadata deletes section (volume replacement occurs at deletion time)
</code></pre>
</div>
@@ -1110,7 +1110,7 @@ can be exacerbated by resource constraints and clock drift.</p>
Hadoop, Apache ZooKeeper and Apache Thrift. We expect Accumulo to
work with versions that are API compatible with those versions.
However this compatibility is not guaranteed because Hadoop, ZooKeeper
-and Thift may not provide guarantees between their own versions. We
+and Thrift may not provide guarantees between their own versions. We
have also found that certain versions of Accumulo and Hadoop included
bugs that greatly affected overall stability. Thrift is particularly
prone to compatibility changes between versions and you must use the
diff --git a/docs/2.0/administration/kerberos.html b/docs/2.0/administration/kerberos.html
index 3116d0c..a77e8c0 100644
--- a/docs/2.0/administration/kerberos.html
+++ b/docs/2.0/administration/kerberos.html
@@ -336,7 +336,7 @@ A centralized key-distribution center (KDC) is the service that coordinates
authentication between a client and a server. Clients and servers use “tickets”,
obtained from the KDC via a password or a special file called a “keytab”, to
communicate with the KDC and prove their identity. A KDC administrator must
-create the principal (name for the client/server identiy) and the password
+create the principal (name for the client/server identity) and the password
or keytab, securely passing the necessary information to the actual user/service.
Properly securing the KDC and generated ticket material is central to the security
model and is mentioned only as a warning to administrators running their own KDC.</p>
@@ -353,7 +353,7 @@ using GSSAPI that Kerberos implements.</p>
<p>Kerberos is a very complicated software application and is deserving of much
more description than can be provided here. An <a href="http://www.roguelynn.com/words/explain-like-im-5-kerberos/">explain like I`m 5</a>
-blog post is very good at distilling the basics, while <a href="http://web.mit.edu/kerberos/">MIT Keberos’s project page</a>
+blog post is very good at distilling the basics, while <a href="http://web.mit.edu/kerberos/">MIT Kerberos’s project page</a>
contains lots of documentation for users or administrators. Various Hadoop “vendors”
also provide free documentation that includes step-by-step instructions for
configuring Hadoop and ZooKeeper (which will be henceforth considered as prerequisites).</p>
@@ -447,7 +447,7 @@ server processes don’t have an interactive console to enter a password into.</
</code></pre>
</div>
-<p>To simplify deployments, at thet cost of security, all Accumulo principals could
+<p>To simplify deployments, at the cost of security, all Accumulo principals could
be globbed into a single keytab</p>
<div class="highlighter-rouge"><pre class="highlight"><code>kadmin.local -q "xst -k accumulo.service.keytab -glob accumulo*"
@@ -953,7 +953,7 @@ on, is extremely important when negotiating an SASL connection. This problem com
servers are not configured to listen on the address denoted by their FQDN.</p>
<p>The values in the Accumulo “hosts” files (In <code class="highlighter-rouge">accumulo/conf</code>: <code class="highlighter-rouge">masters</code>, <code class="highlighter-rouge">monitors</code>, <code class="highlighter-rouge">tservers</code>, <code class="highlighter-rouge">tracers</code>,
-and <code class="highlighter-rouge">gc</code>) should match the instance componentof the Kerberos server principal (e.g. <code class="highlighter-rouge">host</code> in <code class="highlighter-rouge">accumulo/host@EXAMPLE.COM</code>).</p>
+and <code class="highlighter-rouge">gc</code>) should match the instance component of the Kerberos server principal (e.g. <code class="highlighter-rouge">host</code> in <code class="highlighter-rouge">accumulo/host@EXAMPLE.COM</code>).</p>
<p><strong>Q</strong>: After configuring my system for Kerberos, server processes come up normally and I can interact with the system. However,
when I attempt to use the “Recent Traces” page on the Monitor UI I get a stacktrace similar to:</p>
diff --git a/docs/2.0/administration/replication.html b/docs/2.0/administration/replication.html
index b608313..d0698f0 100644
--- a/docs/2.0/administration/replication.html
+++ b/docs/2.0/administration/replication.html
@@ -713,7 +713,7 @@ such as aggregation, which are implemented in a manner resilient to duplication
it is generally not recommended to not configure replication on a table which has Iterators set which are not idempotent.
While the replication implementation can make some simple assertions to try to avoid re-replication of data, it is not
presently guaranteed that all data will only be sent to a peer once. Data will be replicated at least once. Typically,
-this is not a problem as the VersioningIterator will automaticaly deduplicate this over-replication because they will
+this is not a problem as the VersioningIterator will automatically deduplicate this over-replication because they will
have the same timestamp; however, certain Combiners may result in inaccurate aggregations.</p>
<p>As a concrete example, consider a table which has the SummingCombiner configured to sum all values for
@@ -778,7 +778,7 @@ as specified by the column qualifier “local table ID”, has information in th
</code></pre>
</div>
-<p>This entry is created based on a replication entry from the Accumlo metadata table, and is deleted from the replication table
+<p>This entry is created based on a replication entry from the Accumulo metadata table, and is deleted from the replication table
when the WAL has been fully replicated to all remote Accumulo tables.</p>
<h3 id="work-section">Work section</h3>
diff --git a/docs/2.0/administration/ssl.html b/docs/2.0/administration/ssl.html
index 465af19..6d77f32 100644
--- a/docs/2.0/administration/ssl.html
+++ b/docs/2.0/administration/ssl.html
@@ -330,7 +330,7 @@
<p>Accumulo, through Thrift’s TSSLTransport, provides the ability to encrypt
wire communication between Accumulo servers and clients using secure
-sockets layer (SSL). SSL certifcates signed by the same certificate authority
+sockets layer (SSL). SSL certificates signed by the same certificate authority
control the “circle of trust” in which a secure connection can be established.
Typically, each host running Accumulo processes would be given a certificate
which identifies itself.</p>
@@ -451,7 +451,7 @@ keytool -import -trustcacerts -alias server-crt -file server.crt -keystore serve
</div>
<p>The <code class="highlighter-rouge">server.jks</code> file is the Java keystore containing the certificate for a given host. The above
-methods are equivalent whether the certficate is generate for an Accumulo server or a client.</p>
+methods are equivalent whether the certificate is generate for an Accumulo server or a client.</p>
<div class="row" style="margin-top: 20px;">
diff --git a/docs/2.0/development/development_tools.html b/docs/2.0/development/development_tools.html
index 16a71c4..4e678d6 100644
--- a/docs/2.0/development/development_tools.html
+++ b/docs/2.0/development/development_tools.html
@@ -334,7 +334,7 @@
<p><a href="https://static.javadoc.io/org.apache.accumulo/accumulo-minicluster/2.0.0/org/apache/accumulo/minicluster/MiniAccumuloCluster.html">MiniAccumuloCluster</a> is a standalone instance of Apache Accumulo for testing. It will
create Zookeeper and Accumulo processes that write all of their data to a single local
-directory. <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-minicluster/2.0.0/org/apache/accumulo/minicluster/MiniAccumuloCluster.html">MiniAccumuloCluster</a> makes it easy to code agaist a real Accumulo instance.
+directory. <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-minicluster/2.0.0/org/apache/accumulo/minicluster/MiniAccumuloCluster.html">MiniAccumuloCluster</a> makes it easy to code against a real Accumulo instance.
Developers can write realistic-to-end integration tests that mimic the use of a normal
Accumulo instance.</p>
diff --git a/docs/2.0/development/iterators.html b/docs/2.0/development/iterators.html
index b9d52e0..c443f34 100644
--- a/docs/2.0/development/iterators.html
+++ b/docs/2.0/development/iterators.html
@@ -523,7 +523,7 @@ then returns itself.</p>
<span class="n">batch</span><span class="o">.</span><span class="na">add</span><span class="o">(</span><span class="k">new</span> <span class="n">KeyValue</span><span class="o">(</span><span class="n">key</span><span class="o">,</span> <span class="n">val</span><span class="o">)</span>
<span class="k">if</span> <span class="o">(</span><span class="n">systemDataSourcesChanged</span><span class="o">())</span> <span class="o">{</span>
<span class="c1">// code does not show isolation case, which will</span>
- <span class="c1">// keep using same data sources until a row boundry is hit </span>
+ <span class="c1">// keep using same data sources until a row boundary is hit</span>
<span class="n">range</span> <span class="o">=</span> <span class="k">new</span> <span class="n">Range</span><span class="o">(</span><span class="n">key</span><span class="o">,</span> <span class="kc">false</span><span class="o">,</span> <span class="n">range</span><span class="o">.</span><span class="na">endKey</span><span class="o">(),</span> <span class="n">range</span><span class="o">.</span><span class="na">endKeyInclusive</span><span class="o">());</span>
<span class="k">break</span><span class="o">;</span>
<span class="o">}</span>
@@ -688,15 +688,15 @@ Iterator’s implementation of seek.</p>
<h3 id="take-caution-in-constructing-new-data-in-an-iterator">Take caution in constructing new data in an Iterator</h3>
-<p>Implementations of Iterator might be tempted to open <a href="/org/apache/accumulo/core/client/BatchWriter.html">BatchWriters</a> inside of an Iterator as a means
+<p>Implementations of Iterator might be tempted to open <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/BatchWriter.html">BatchWriters</a> inside of an Iterator as a means
to implement triggers for writing additional data outside of their client application. The lifecycle of an Iterator
is <em>not</em> managed in such a way that guarantees that this is safe nor efficient. Specifically, there
is no way to guarantee that the internal ThreadPool inside of the BatchWriter is closed (and the thread(s)
-are reaped) without calling the close() method. <code class="highlighter-rouge">close</code>‘ing and recreating a <a href="/org/apache/accumulo/core/client/BatchWriter.html">BatchWriter</a> after every
+are reaped) without calling the close() method. <code class="highlighter-rouge">close</code>‘ing and recreating a <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/BatchWriter.html">BatchWriter</a> after every
Key-Value pair is also prohibitively performance limiting to be considered an option.</p>
<p>The only safe way to generate additional data in an Iterator is to alter the current Key-Value pair.
-For example, the <a href="/org/apache/accumulo/core/iterators/user/WholeRowIterator.html">WholeRowIterator</a> serializes the all of the Key-Values pairs that fall within each
+For example, the <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/iterators/user/WholeRowIterator.html">WholeRowIterator</a> serializes the all of the Key-Values pairs that fall within each
row. A safe way to generate more data in an Iterator would be to construct an Iterator that is
“higher” (at a larger priority) than the WholeRowIterator, that is, the Iterator receives the Key-Value pairs which are
a serialization of many Key-Value pairs. The custom Iterator could deserialize the pairs, compute
diff --git a/docs/2.0/development/proxy.html b/docs/2.0/development/proxy.html
index d49cedc..8d07a40 100644
--- a/docs/2.0/development/proxy.html
+++ b/docs/2.0/development/proxy.html
@@ -400,7 +400,7 @@ to how generate source from a thrift file.</p>
<h3 id="thrift-library">Thrift library</h3>
<p>Language-specific Thrift libraries can be installed using an OS or language package manager (i.e gem, pip, etc).
-For example, <code class="highlighter-rouge">pip install thrift</code> will install Python-specific thrift libaries on your machine.</p>
+For example, <code class="highlighter-rouge">pip install thrift</code> will install Python-specific thrift libraries on your machine.</p>
<h2 id="proxy-client-examples">Proxy Client Examples</h2>
diff --git a/docs/2.0/development/security.html b/docs/2.0/development/security.html
index e041213..0be45bc 100644
--- a/docs/2.0/development/security.html
+++ b/docs/2.0/development/security.html
@@ -445,7 +445,7 @@ authorization, and permission handling.</p>
<p>Authentication verifies the identity of a user. In Accumulo, authentication occurs when
the <code class="highlighter-rouge">getConnector</code> method of <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/Instance.html">Instance</a> is called with a principal (i.e username)
and an <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/security/tokens/AuthenticationToken.html">AuthenticationToken</a> which is an interface with multiple implementations. The most
-common implementation is <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/security/tokens/PasswordToken.html">PasswordToken</a> which is the default authenticaton method for Accumulo
+common implementation is <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/security/tokens/PasswordToken.html">PasswordToken</a> which is the default authentication method for Accumulo
out of the box.</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="n">Instance</span> <span class="n">instance</span> <span class="o">=</span> <span class="k">new</span> <span class="n">ZooKeeperInstance</span><span class="o">(</span><span class="s">"myinstance"</span><span class="o">,</span> <span class="s">"zookeeper1,zookeeper2"</span><span class="o">);</span>
diff --git a/docs/2.0/getting-started/quick-install.html b/docs/2.0/getting-started/quick-install.html
index c7ba6e5..f154a69 100644
--- a/docs/2.0/getting-started/quick-install.html
+++ b/docs/2.0/getting-started/quick-install.html
@@ -397,7 +397,7 @@ Hadoop or Zookeeper, you may need to modify how the <code class="highlighter-rou
<li>
<p>Accumulo tablet servers are configured by default to use 1GB of memory (768MB is allocated to
JVM and 256MB is allocated for native maps). Native maps are allocated memory equal to 33% of
-the tserver JVM heap. The table below can be used if you would like to change tsever memory
+the tserver JVM heap. The table below can be used if you would like to change tserver memory
usage in the <code class="highlighter-rouge">JAVA_OPTS</code> section of <code class="highlighter-rouge">accumulo-env.sh</code>:</p>
<table>
@@ -478,7 +478,7 @@ testing or if you are not using a cluster management tool in production.</p>
<h3 id="run-accumulo-processes">Run Accumulo processes</h3>
-<p>Start Accumulo processes (tserver, master, moniitor, etc) using command below:</p>
+<p>Start Accumulo processes (tserver, master, monitor, etc) using command below:</p>
<div class="highlighter-rouge"><pre class="highlight"><code>accumulo tserver
</code></pre>
diff --git a/docs/2.0/getting-started/shell.html b/docs/2.0/getting-started/shell.html
index e5e4878..71e7211 100644
--- a/docs/2.0/getting-started/shell.html
+++ b/docs/2.0/getting-started/shell.html
@@ -355,7 +355,7 @@ root@myinstance>
<h2 id="basic-administration">Basic Administration</h2>
-<p>The <code class="highlighter-rouge">tables</code> command will list all existings tables.</p>
+<p>The <code class="highlighter-rouge">tables</code> command will list all existing tables.</p>
<div class="highlighter-rouge"><pre class="highlight"><code>root@myinstance> tables
accumulo.metadata
diff --git a/docs/2.0/getting-started/table_design.html b/docs/2.0/getting-started/table_design.html
index 9b76557..92f52e1 100644
--- a/docs/2.0/getting-started/table_design.html
+++ b/docs/2.0/getting-started/table_design.html
@@ -537,7 +537,7 @@ including nodes, their attributes, and connections to other nodes.</p>
<p>Rather than storing individual events, Entity-Attribute or Graph tables store
aggregate information about the entities involved in the events and the
-relationships between entities. This is often preferrable when single events aren’t
+relationships between entities. This is often preferable when single events aren’t
very useful and when a continuously updated summarization is desired.</p>
<p>The physical schema for an entity-attribute or graph table is as follows:</p>
diff --git a/docs/2.0/troubleshooting/advanced.html b/docs/2.0/troubleshooting/advanced.html
index 9263dad..6c4cf64 100644
--- a/docs/2.0/troubleshooting/advanced.html
+++ b/docs/2.0/troubleshooting/advanced.html
@@ -441,7 +441,7 @@ due to the JVM running out of memory, or being swapped out to disk.</p>
<h2 id="hdfs-failures">HDFS Failures</h2>
-<p><strong>I had disasterous HDFS failure. After bringing everything back up, several tablets refuse to go online.</strong></p>
+<p><strong>I had disastrous HDFS failure. After bringing everything back up, several tablets refuse to go online.</strong></p>
<p>Data written to tablets is written into memory before being written into indexed files. In case the server
is lost before the data is saved into a an indexed file, all data stored in memory is first written into a
@@ -505,7 +505,7 @@ but the basic approach is:</p>
<li>Stop all accumulo processes on all nodes</li>
<li>Move the accumulo directory in HDFS out of the way:
$ hadoop fs -mv /accumulo /corrupt</li>
- <li>Re-initalize accumulo</li>
+ <li>Re-initialize accumulo</li>
<li>Recreate tables, users and permissions</li>
<li>Import the directories under <code class="highlighter-rouge">/corrupt/tables/<id></code> into the new instance</li>
</ul>
@@ -544,7 +544,7 @@ table files or if they are metadata table files.</p>
operations is to replace the missing file with an ``empty’’ file so that
references to the file in the METADATA table and within the tablet server
hosting the file can be resolved by Accumulo. An empty file can be created using
-the CreateEmpty utiity:</p>
+the CreateEmpty utility:</p>
<div class="highlighter-rouge"><pre class="highlight"><code>$ accumulo org.apache.accumulo.core.file.rfile.CreateEmpty /path/to/empty/file/empty.rf
</code></pre>
@@ -587,7 +587,7 @@ WAL file, never being able to succeed.</p>
<p>In the cases where the WAL file’s original contents are unrecoverable or some degree
of data loss is acceptable (beware if the WAL file contains updates to the Accumulo
-metadat table!), the following process can be followed to create an valid, empty
+metadata table!), the following process can be followed to create an valid, empty
WAL file. Run the following commands as the Accumulo unix user (to ensure that
the proper file permissions in HDFS)</p>
@@ -676,7 +676,7 @@ omission of new data.</p>
<p>Yes, you can recover them by running the LocalWALRecovery utility (not available in 1.8 and later) on each node that needs recovery performed. The utility
will default to using the directory specified by <code class="highlighter-rouge">logger.dir.walog</code> in your configuration, or can be
-overriden by using the <code class="highlighter-rouge">--local-wal-directories</code> option on the tool. It can be invoked as follows:</p>
+overridden by using the <code class="highlighter-rouge">--local-wal-directories</code> option on the tool. It can be invoked as follows:</p>
<div class="highlighter-rouge"><pre class="highlight"><code>accumulo org.apache.accumulo.tserver.log.LocalWALRecovery
</code></pre>
diff --git a/feed.xml b/feed.xml
index 0af425f..c8acede 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, 01 Nov 2017 17:53:41 -0400</pubDate>
- <lastBuildDate>Wed, 01 Nov 2017 17:53:41 -0400</lastBuildDate>
+ <pubDate>Fri, 03 Nov 2017 12:39:26 -0400</pubDate>
+ <lastBuildDate>Fri, 03 Nov 2017 12:39:26 -0400</lastBuildDate>
<generator>Jekyll v3.5.2</generator>
@@ -152,8 +152,8 @@ vim conf/muchos.props
<h2 id="conclusion">Conclusion</h2>
-<p>Uno and Muchos automate installing Accumulo for developmment and testing. While not recommended for production
-use at this time, Muchos is a great reference for running Accumulo in production. System admistrators can
+<p>Uno and Muchos automate installing Accumulo for development and testing. While not recommended for production
+use at this time, Muchos is a great reference for running Accumulo in production. System administrators can
reference the <a href="https://www.ansible.com/">Ansible</a> code in Muchos to automate management of their own clusters.</p>
</description>
@@ -603,7 +603,7 @@ in the output generated by <a href="https://github.com/apache/accumulo/b
<p><a href="/images/blog/201702_security/accumuloFiles.png"><img src="/images/blog/201702_security/accumuloFiles.png" alt="" width="800px" /></a></p>
<p>As can be seen in the plots above, the different security settings have
-relatively consistent, discernable median run characteristics. The big
+relatively consistent, discernible median run characteristics. The big
dip in each TOTAL_INGEST coincides with a large number of major
compactions, a rate decrease for TABLE_RECS, and a decrease in
AVG_FILES/TABLET.</p>
@@ -714,7 +714,7 @@ fixed in <a href="https://issues.apache.org/jira/browse/ACCUMULO-4572&qu
<h3 id="hostregextableloadbalancer-used-stale-information">HostRegexTableLoadBalancer used stale information</h3>
-<p>The HostRegexTableLoadBalander maintains an internal mapping of tablet
+<p>The HostRegexTableLoadBalancer maintains an internal mapping of tablet
server pools and tablet server status. It was updated at a
configurable interval initially as an optimization. Unfortunately it
had the negative side effect of providing the assignment and balance
@@ -1206,9 +1206,9 @@ bootstrap_hdfs.sh config.sh start-daemon.sh s
</div>
<p>The number of scripts made it difficult to know which scripts to use. If you added the <code class="highlighter-rouge">bin/</code> directory to your
-<code class="highlighter-rouge">PATH</code>, it could add unecessary commands to your PATH or cause commands to be overriden due generic names
+<code class="highlighter-rouge">PATH</code>, it could add unnecessary commands to your PATH or cause commands to be overridden due generic names
(like ‘start-all.sh’). The number of scripts were reduced by removing scripts that are no longer used and combining
-scripts with similiar functionality.</p>
+scripts with similar functionality.</p>
<p>Starting with 2.0.0, Accumulo will only have 4 scripts in its <code class="highlighter-rouge">bin/</code> directory:</p>
@@ -1315,7 +1315,7 @@ Services:
monitor Accumulo monitor
master Accumulo master
tserver Accumulo tserver
- tracer Accumulo tracter
+ tracer Accumulo tracer
Commands:
start Starts service
diff --git a/release/accumulo-1.5.1/index.html b/release/accumulo-1.5.1/index.html
index f00819a..9e7f73b 100644
--- a/release/accumulo-1.5.1/index.html
+++ b/release/accumulo-1.5.1/index.html
@@ -279,7 +279,7 @@ to disk before unloading a Tablet.</p>
<p>When using Accumulo 1.5 and Hadoop 2, Accumulo will call hsync() on HDFS.
Calling hsync improves durability by ensuring data is on disk (where other older
Hadoop versions might lose data in the face of power failure); however, calling
-hsync frequently does noticably slow writes. A simple work around is to increase
+hsync frequently does noticeably slow writes. A simple work around is to increase
the value of the tserver.mutation.queue.max configuration parameter via accumulo-site.xml.</p>
<p>A value of “4M” is a better recommendation, and memory consumption will increase by
diff --git a/release/accumulo-1.5.2/index.html b/release/accumulo-1.5.2/index.html
index 72739d1..a83159a 100644
--- a/release/accumulo-1.5.2/index.html
+++ b/release/accumulo-1.5.2/index.html
@@ -251,7 +251,7 @@ parameter, like <a href="https://issues.apache.org/jira/browse/ACCUMULO-2360">AC
<h3 id="offline-tables-can-prevent-tablet-balancing">Offline tables can prevent tablet balancing</h3>
<p>Before 1.5.2, when a table with many tablets was created, ingested into, and
-taken offline, tablet balancing may have stoppped. This would happen if there
+taken offline, tablet balancing may have stopped. This would happen if there
were tablet migrations for the table, because the migrations couldn’t occur.
The balancer will not run when there are outstanding migrations; therefore, a
system could become unbalanced. <a href="https://issues.apache.org/jira/browse/ACCUMULO-2694">ACCUMULO-2694</a> introduces a fix to ensure
diff --git a/release/accumulo-1.6.0/index.html b/release/accumulo-1.6.0/index.html
index e78c92f..ca72d15 100644
--- a/release/accumulo-1.6.0/index.html
+++ b/release/accumulo-1.6.0/index.html
@@ -384,7 +384,7 @@ If this is happening often a possible work around is to set <code class="highlig
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1407" title="Fix documentation for deleterows">ACCUMULO-1407</a> Fix documentation for deleterows</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1428" title="Document native maps">ACCUMULO-1428</a> Document native maps</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1946" title="Include dfs.datanode.synconclose in hdfs configuration documentation">ACCUMULO-1946</a> Include dfs.datanode.synconclose in hdfs configuration documentation</li>
- <li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1956" title="Add section on decomissioning or adding nodes to an Accumulo cluster">ACCUMULO-1956</a> Add section on decomissioning or adding nodes to an Accumulo cluster</li>
+ <li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1956" title="Add section on decommissioning or adding nodes to an Accumulo cluster">ACCUMULO-1956</a> Add section on decommissioning or adding nodes to an Accumulo cluster</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2441" title="Document internal state stored in RFile names">ACCUMULO-2441</a> Document internal state stored in RFile names</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2590" title="Update public API in readme to clarify what's included">ACCUMULO-2590</a> Update public API in readme to clarify what’s included</li>
</ul>
diff --git a/release/accumulo-1.6.1/index.html b/release/accumulo-1.6.1/index.html
index 8f6f9f7..55e648a 100644
--- a/release/accumulo-1.6.1/index.html
+++ b/release/accumulo-1.6.1/index.html
@@ -242,7 +242,7 @@ parameter, like <a href="https://issues.apache.org/jira/browse/ACCUMULO-2360">AC
<h3 id="offline-tables-can-prevent-tablet-balancing">Offline tables can prevent tablet balancing</h3>
<p>Before 1.6.1, when a table with many tablets was created, ingested into, and
-taken offline, tablet balancing may have stoppped. This would happen if there
+taken offline, tablet balancing may have stopped. This would happen if there
were tablet migrations for the table, because the migrations couldn’t occur.
The balancer will not run when there are outstanding migrations; therefore, a
system could become unbalanced. <a href="https://issues.apache.org/jira/browse/ACCUMULO-2694">ACCUMULO-2694</a> introduces a fix to ensure
diff --git a/release/accumulo-1.6.6/index.html b/release/accumulo-1.6.6/index.html
index 6176db5..9fa7c1b 100644
--- a/release/accumulo-1.6.6/index.html
+++ b/release/accumulo-1.6.6/index.html
@@ -205,11 +205,11 @@ identical keys and no timestamp would exhibit different behaviour depending on
whether native maps were enabled or not. This behaviour would result in hidden
mutations with native maps, and has been corrected.</p>
-<h3 id="open-wal-files-could-prevent-datanode-decomission">Open WAL files could prevent DataNode decomission</h3>
+<h3 id="open-wal-files-could-prevent-datanode-decommission">Open WAL files could prevent DataNode decommission</h3>
<p>An improvement was introduced to allow a max age before WAL files would be
automatically rolled. Without a max age, they could stay open for writing
-indefinitely, blocking the Hadoop DataNode decomissioning process. For more
+indefinitely, blocking the Hadoop DataNode decommissioning process. For more
information, see <a href="https://issues.apache.org/jira/browse/ACCUMULO-4004">ACCUMULO-4004</a>.</p>
<h3 id="remove-unnecessary-copy-of-cached-rfile-index-blocks">Remove unnecessary copy of cached RFile index blocks</h3>
diff --git a/release/accumulo-1.7.0/index.html b/release/accumulo-1.7.0/index.html
index 3e94ee4..4a2ad78 100644
--- a/release/accumulo-1.7.0/index.html
+++ b/release/accumulo-1.7.0/index.html
@@ -283,7 +283,7 @@ files in a table.</p>
<p>These provided convenience options to select files execute using a specialized
compaction strategy. Options were also added to the shell to specify an
-arbitrary compaction strategy. The option to specify an arbitrry compaction
+arbitrary compaction strategy. The option to specify an arbitrary compaction
strategy is mutually exclusive with the file selection and file creation
options, since those options are unique to the specialized compaction strategy
provided. See <code class="highlighter-rouge">compact --help</code> in the shell for the available options.</p>
diff --git a/release/accumulo-1.7.2/index.html b/release/accumulo-1.7.2/index.html
index 727f5b6..c8781e8 100644
--- a/release/accumulo-1.7.2/index.html
+++ b/release/accumulo-1.7.2/index.html
@@ -184,9 +184,9 @@ upgrade to 1.7 should consider 1.7.2 as a starting point.</p>
<p>There was a bug (<a href="https://issues.apache.org/jira/browse/ACCUMULO-4148">ACCUMULO-4148</a>) where multiple put calls with identical keys and no timestamp would exhibit different behaviour depending on whether native maps were enabled or not. This behaviour would result in hidden mutations with native maps, and has been corrected.</p>
-<h3 id="open-wal-files-could-prevent-datanode-decomission">Open WAL files could prevent DataNode decomission</h3>
+<h3 id="open-wal-files-could-prevent-datanode-decommission">Open WAL files could prevent DataNode decommission</h3>
-<p>An improvement was introduced to allow a max age before WAL files would be automatically rolled. Without a max age, they could stay open for writing indefinitely, blocking the Hadoop DataNode decomissioning process. For more information, see <a href="https://issues.apache.org/jira/browse/ACCUMULO-4004">ACCUMULO-4004</a>.</p>
+<p>An improvement was introduced to allow a max age before WAL files would be automatically rolled. Without a max age, they could stay open for writing indefinitely, blocking the Hadoop DataNode decommissioning process. For more information, see <a href="https://issues.apache.org/jira/browse/ACCUMULO-4004">ACCUMULO-4004</a>.</p>
<h3 id="remove-unnecessary-copy-of-cached-rfile-index-blocks">Remove unnecessary copy of cached RFile index blocks</h3>
diff --git a/release/accumulo-1.8.0/index.html b/release/accumulo-1.8.0/index.html
index cd7627a..1a68d9b 100644
--- a/release/accumulo-1.8.0/index.html
+++ b/release/accumulo-1.8.0/index.html
@@ -180,7 +180,7 @@ very seriously and have invested much time to ensure that we meet the promises s
<h3 id="speed-up-wal-roll-overs">Speed up WAL roll overs</h3>
<p>Performance of writing mutations is improved by refactoring the
-bookeeping required for Write-Ahead Log (WAL) files and by creating a
+bookkeeping required for Write-Ahead Log (WAL) files and by creating a
standby WAL for faster switching when the log is full. This was a
substantial refactor in the way WALs worked, but smoothes overall
ingest performance in addition to provides a increase in write speed
@@ -275,7 +275,7 @@ harness can be used directly by users as a supplemental tool to unit tests and i
<p>Previously, the default port for the monitor was 50095. You will need to update your links to point to port 9995. The default
port for the GC process was also changed from 50091 to 9998, although this an RPC port used internally and automatically discovered.
These default ports were changed because the previous defaults fell in the Linux Ephemeral port range. This means that the operating
-system, when a port in this range was unusued, would allocate this port for dynamic network communication. This has the side-effect of
+system, when a port in this range was unused, would allocate this port for dynamic network communication. This has the side-effect of
temporal bind issues when trying to start these services (as the operating
system might have allocated them elsewhere). By moving these
defaults out of the ephemeral range, we can guarantee that the Monitor and GC
@@ -290,7 +290,7 @@ will reliably start. These values are still configurable by setting
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2883">ACCUMULO-2883</a> API to fetch current tablet assignments</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-3871">ACCUMULO-3871</a> Support for running integration tests in MapReduce</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-3920">ACCUMULO-3920</a> Deprecate the MockAccumulo class and remove usage in our tests</li>
- <li><a href="https://issues.apache.org/jira/browse/ACCUMULO-4339">ACCUMULO-4339</a> Make hadoop-minicluster optional dependency of acccumulo-minicluster</li>
+ <li><a href="https://issues.apache.org/jira/browse/ACCUMULO-4339">ACCUMULO-4339</a> Make hadoop-minicluster optional dependency of accumulo-minicluster</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-4318">ACCUMULO-4318</a> BatchWriter, ConditionalWriter, and ScannerBase now extend AutoCloseable</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-4326">ACCUMULO-4326</a> Value constructor now accepts Strings (and Charsequences)</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-4354">ACCUMULO-4354</a> Bump dependency versions to include gson, jetty, and sl4j</li>
diff --git a/release/accumulo-1.8.1/index.html b/release/accumulo-1.8.1/index.html
index ad53a1e..42bd483 100644
--- a/release/accumulo-1.8.1/index.html
+++ b/release/accumulo-1.8.1/index.html
@@ -225,7 +225,7 @@ fixed in <a href="https://issues.apache.org/jira/browse/ACCUMULO-4572">ACCUMULO-
<h3 id="hostregextableloadbalancer-used-stale-information">HostRegexTableLoadBalancer used stale information</h3>
-<p>The HostRegexTableLoadBalander maintains an internal mapping of tablet
+<p>The HostRegexTableLoadBalancer maintains an internal mapping of tablet
server pools and tablet server status. It was updated at a
configurable interval initially as an optimization. Unfortunately it
had the negative side effect of providing the assignment and balance
--
To stop receiving notification emails like this one, please contact
['"commits@accumulo.apache.org" <co...@accumulo.apache.org>'].