svn commit: r923739 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.6.1.html

[bu...@apache.org]

Author: buildbot
Date: Fri Sep 26 20:07:28 2014
New Revision: 923739

Log:
Staging update by buildbot for accumulo

Modified:
    websites/staging/accumulo/trunk/content/   (props changed)
    websites/staging/accumulo/trunk/content/release_notes/1.6.1.html

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Sep 26 20:07:28 2014
@@ -1 +1 @@
-1627862
+1627870

Modified: websites/staging/accumulo/trunk/content/release_notes/1.6.1.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.6.1.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.6.1.html Fri Sep 26 20:07:28 2014
@@ -192,20 +192,15 @@ Latest 1.5 release: <strong>1.5.1</stron
 
     <h1 class="title">Apache Accumulo 1.5.2 Release Notes</h1>
 
-    <p>Apache Accumulo 1.5.2 is a maintenance release on the 1.5 version branch.
-This release contains changes from over 100 issues, comprised of bug fixes
-(client side and server side), new test cases, and updated Hadoop support
-contributed by over 30 different contributors and committers.
-As this is a maintenance release, Apache Accumulo 1.5.2 has no client API 
-incompatibilities over Apache Accumulo 1.5.0 and 1.5.1 and requires no manual upgrade 
-process. Users of 1.5.0 or 1.5.1 are strongly encouraged to update as soon as possible 
-to benefit from the improvements.</p>
-<p>Users who are new to Accumulo are encouraged to use a 1.6 release as opposed
-to the 1.5 line as development has already shifted towards the 1.6 line. For those
-who cannot or do not want to upgrade to 1.6, 1.5.2 is still an excellent choice
-over earlier versions in the 1.5 line.</p>
+    <p>Apache Accumulo 1.6.1 is a maintenance release on the 1.6 version branch.
+This release contains changes from over 175 issues, comprised of bug-fixes, performance
+improvements and better test cases. As this is a maintenance release, Apache Accumulo
+1.6.1 has no client API  incompatibilities over Apache Accumulo 1.6.0. Users of 1.6.0
+are strongly encouraged to update as soon as possible to benefit from the improvements.</p>
+<p>New users are encouraged to use this release over 1.6.0 or any other older releases.</p>
 <h2 id="performance-improvements">Performance Improvements</h2>
-<p>Apache Accumulo 1.5.2 includes a number of performance-related fixes over previous versions.</p>
+<p>Apache Accumulo 1.6.1 includes a number of performance-related fixes over previous versions.
+Many of these improvements were also included in the recently released Apache Accumulo 1.5.2.</p>
 <h3 id="write-ahead-log-sync-performance">Write-Ahead Log sync performance</h3>
 <p>The Write-Ahead Log (WAL) files are used to ensure durability of updates made to Accumulo.
 A sync is called on the file in HDFS to make sure that the changes to the WAL are persisted
@@ -238,27 +233,23 @@ that lets users to change the HDFS sync 
 of <em>hsync</em> may result in about a 30% increase in ingest performance.</p>
 <p>For users upgrading from Hadoop-1 or Hadoop-0.20 releases, <em>hflush</em> is the equivalent of how
 sync was implemented in these older versions of Hadoop and should give comparable performance.</p>
-<h3 id="server-side-mutation-queue-size">Server-side mutation queue size</h3>
-<p>When users desire writes to be as durable as possible, using <em>hsync</em>, the ingest performance
-of the system can be improved by increasing the tserver.mutation.queue.max property. The cost
-of this change is that it will cause TabletServers to use additional memory per writer. In 1.5.1,
-the value of this parameter defaulted to a conservative 256K, which resulted in sub-par ingest
-performance.</p>
-<p>1.5.2 and <a href="https://issues.apache.org/jira/browse/ACCUMULO-3018">ACCUMULO-3018</a> increases this buffer to 1M which has a noticeable positive impact on
-ingest performance with a minimal increase in TabletServer memory usage.</p>
+<h2 id="other-improvements">Other improvements</h2>
+<h3 id="use-of-hadoop-credentialproviders">Use of Hadoop CredentialProviders</h3>
+<p>Apache Hadoop 2.6.0 introduced a new API aimed at providing ways to separate sensitive values
+from being stored in plaintext as a part of <a href="https://issues.apache.org/jira/browse/HADOOP-10607">HADOOP-10607</a>. Accumulo has had two sensitive
+configuration properties stored in <em>accumulo-site.xml</em> for every standard installation: instance.secret
+and trace.token.property.password. If either of these properties are compromised, it could lead to
+unwanted access of Accumulo. <a href="https://issues.apache.org/jira/browse/ACCUMULO-2464">ACCUMULO-2464</a> modifies Accumulo so that it can stored any sensitive
+configuration properties in a Hadoop CredentialProvider. With sensitive values removed from accumulo-site.xml,
+it can be shared without concern and security can be focused solely on the CredentialProvider.</p>
 <h2 id="notable-bug-fixes">Notable Bug Fixes</h2>
-<h3 id="fixes-mapreduce-package-name-change">Fixes MapReduce package name change</h3>
-<p>1.5.1 inadvertently included a change to RangeInputSplit which created an incompatibility
-with 1.5.0. The original class has been restored to ensure that users accessing
-the RangeInputSplit class do not have to alter their client code. See <a href="https://issues.apache.org/jira/browse/ACCUMULO-2586">ACCUMULO-2586</a> for
-more information</p>
 <h3 id="add-configurable-maximum-frame-size-to-thrift-proxy">Add configurable maximum frame size to Thrift proxy</h3>
 <p>The Thrift proxy server was subject to memory exhaustion, typically
 due to bad input, where the server would attempt to allocate a very large
 buffer and die in the process. <a href="https://issues.apache.org/jira/browse/ACCUMULO-2658">ACCUMULO-2658</a> introduces a configuration
 parameter, like <a href="https://issues.apache.org/jira/browse/ACCUMULO-2360">ACCUMULO-2360</a>, to prevent this error.</p>
 <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
+<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
 were tablet migrations for the table, because the migrations couldn't occur.
 The balancer will not run when there are outstanding migrations; therefore, a
@@ -278,21 +269,34 @@ fixes the serialization and adds some ad
 loop due to a constraint violation. This directly prevents scans from completing,
 but will also hang compactions. <a href="https://issues.apache.org/jira/browse/ACCUMULO-3096">ACCUMULO-3096</a> fixes the issue so that the
 constraint no longer hangs the entire system.</p>
+<h3 id="unable-to-upgrade-cleanly-from-15">Unable to upgrade cleanly from 1.5</h3>
+<p>When upgrading a table from 1.5.1 to 1.6.0, a user experienced an error where the table
+never came online. <a href="https://issues.apache.org/jira/browse/ACCUMULO-2974">ACCUMULO-2974</a> fixes an issue from the change of file references
+stored as absolute paths instead of relative paths in the Accumulo metadata table.</p>
+<h3 id="guava-dependency-changed">Guava dependency changed</h3>
+<p><a href="https://issues.apache.org/jira/browse/ACCUMULO-3100">ACCUMULO-3100</a> lowered the dependency on Guava from 15.0.1 to 14.0. This dependency
+now matches what Hadoop is depending on for the 2.x.y version line. Depending on a newer
+version of Guava introduces many issues stemming from deprecated classes in use by Hadoop
+which have been removed. While installations of Accumulo will likely work as expected with
+newer versions of Guava on the classpath (because the Hadoop processes will have their own
+classpath), use of MiniDfsClusters with the new Guava version will result in errors.</p>
+<p>Users can attempt to use a newer version of Guava on the Accumulo server classpath; however,
+the success is dependent on Hadoop client libraries not using (missing) Guava methods internally.</p>
+<h3 id="scanners-eat-interruptedexception">Scanners eat InterruptedException</h3>
+<p>Scanners previously consumed InterruptedExceptions and did not exit after. In multi-threaded
+environments, this is very problematic as there is no means to stop the Scanner from reading data.
+<a href="https://issues.apache.org/jira/browse/ACCUMULO-3030">ACCUMULO-3030</a> fixes the Scanner so that interrupts are observed and the Scanner exits as expected.</p>
 <h2 id="documentation">Documentation</h2>
 <p>The following documentation updates were made: </p>
 <ul>
-<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2540">ACCUMULO-2540</a></li>
 <li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2767">ACCUMULO-2767</a></li>
 <li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2796">ACCUMULO-2796</a></li>
-<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2443">ACCUMULO-2443</a></li>
-<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-3008">ACCUMULO-3008</a></li>
 <li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2919">ACCUMULO-2919</a></li>
+<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-3008">ACCUMULO-3008</a></li>
 <li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2874">ACCUMULO-2874</a></li>
-<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2653">ACCUMULO-2653</a></li>
-<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2437">ACCUMULO-2437</a></li>
+<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2821">ACCUMULO-2821</a></li>
+<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-3097">ACCUMULO-3097</a></li>
 <li><a href="https://issues.apache.org/jira/browse/ACCUMULO-3097">ACCUMULO-3097</a></li>
-<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2499">ACCUMULO-2499</a></li>
-<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1669">ACCUMULO-1669</a></li>
 </ul>
 <h2 id="testing">Testing</h2>
 <p>Each unit and functional test only runs on a single node, while the RandomWalk and Continuous Ingest tests run