Author: buildbot
Date: Wed Apr 9 16:32:55 2014
New Revision: 905586
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/release_notes/1.6.0.html
Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Apr 9 16:32:55 2014
@@ -1 +1 @@
-1586016
+1586018
Modified: websites/staging/accumulo/trunk/content/release_notes/1.6.0.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.6.0.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.6.0.html Wed Apr 9
16:32:55 2014
@@ -92,15 +92,15 @@
<div id="content">
<h1 class="title"></h1>
<p><strong>DRAFT 1.6.0 RELEASE NOTES</strong></p>
-<p>Apache Accumulo 1.6.0</p>
-<p>This document is a work in progress.</p>
-<p>TODO recommend hadoop 2</p>
+<p>Apache Accumulo 1.6.0 adds some major new features and fixes many bugs.
This release contains changes from 609 issues contributed by 36 contributors
and committers. </p>
+<p>TODO paragraph on API changes</p>
+<p>Accumulo 1.6.0 runs on Hadoop 1, however Hadoop 2 with HA namenode is
recommended for production systems. In addition to HA, Hadoop 2 also offers
better data durability guarantees, in the case when nodes lose power, than
Hadoop 1.</p>
<h2 id="notable-improvements">Notable Improvements</h2>
<h3 id="multiple-namenode-support">Multiple namenode support</h3>
<p><a href="http://research.google.com/archive/bigtable.html";>BigTable's</a>
design allows for its internal metadata to automatically spread across multiple
nodes. Accumulo has followed this design and scales very well as a result.
There is one impediment to scaling though, and this is the HDFS namenode.
There are two problems with the namenode when it comes to scaling. First, the
namenode stores all of its filesystem metadata in memory on a single machine.
This introduces an upper bound on the number of files Accumulo can have.
Second, there is an upper bound on the number of file operations per second
that a single namenode can support. For example, a namenode can only support a
few thousand delete or create file request per second. </p>
<p>To overcome this bottleneck, support for multiple namenodes was added under
<a href="https://issues.apache.org/jira/browse/ACCUMULO-118"; title="Multiple
namenode support">ACCUMULO-118</a>. This change allows Accumulo to store its
files across multiple namenodes. To use this feature, place comma separated
list of namenode URIs in the new <em>instance.volumes</em> configuration
property in accumulo-site.xml. When upgrading to 1.6.0 and multiple namenode
support is desired, modify this setting <strong>only</strong> after a
successful upgrade.</p>
<h3 id="table-namespaces">Table namespaces</h3>
-<p>Administering an Accumulo instance with many tables is cumbersome. To ease
this, <a href="https://issues.apache.org/jira/browse/ACCUMULO-802"; title="Table
namespaces">ACCUMULO-802</a> introduced table namespaces which allow tables to
be grouped into logical collections. This allows configuration and permission
changes to made to a namespace, which will apply to all of its tables. Example
use cases are ... TODO</p>
+<p>Administering an Accumulo instance with many tables is cumbersome. To ease
this, <a href="https://issues.apache.org/jira/browse/ACCUMULO-802"; title="Table
namespaces">ACCUMULO-802</a> introduced table namespaces which allow tables to
be grouped into logical collections. This allows configuration and permission
changes to made to a namespace, which will apply to all of its tables.</p>
<h3 id="conditional-mutations">Conditional Mutations</h3>
<p>Accumulo now offers a way to make atomic read,modify,write row changes from
the client side. Atomic test and set row operations make this possible. <a
href="https://issues.apache.org/jira/browse/ACCUMULO-1000"; title="Conditional
Mutations">ACCUMULO-1000</a> added conditional mutations and a conditional
writer. A conditional mutation has tests on columns that must pass before any
changes are made. These test are executed in server processes while a row lock
is held. Below is a simple example of making atomic row changes using
conditional mutations.</p>
<ol>
@@ -138,6 +138,7 @@ ticket that contains numerous fixes to e
<h3 id="other-notable-changes">Other notable changes</h3>
<ul>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-842"; title="Add
FATE administration to shell">ACCUMULO-842</a> Added FATE administration to
shell</li>
+<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1442";
title="Replace JLine with JLine2">ACCUMULO-1442</a> JLine2 support was added to
the shell. This adds features like history search and other nice things GNU
Readline has. </li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1481"; title="Root
tablet in its own table">ACCUMULO-1481</a> The root tablet is now the root
table.</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1566"; title="Add
ability for client to start Scanner readahead immediately">ACCUMULO-1566</a>
When read-ahead starts in the scanner is now configurable.</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1667"; title="Allow
On/Offline Command To Execute Synchronously">ACCUMULO-1667</a> Added a
synchronous version of online and offline table</li>
@@ -148,14 +149,11 @@ ticket that contains numerous fixes to e
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2360"; title="Need
a way to configure TNonblockingServer.maxReadBufferBytes to prevent
OOMs">ACCUMULO-2360</a> Allow configuration of the maximum thrift message size
a server will read.</li>
</ul>
<h2 id="notable-bug-fixes">Notable Bug Fixes</h2>
-<p>TODO kturner looked at bugs w/ fix version of 1.6.0 and a non-empty affects
version and selected ones he thought were relevant to users.... need others
devs to do this
-TODO some bugs may be unintelligible to end users... either improve the issue
descritpion or remove from list</p>
<ul>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-324";
title="System/site constraints and iterators should NOT affect the METADATA
table">ACCUMULO-324</a> System/site constraints and iterators should NOT affect
the METADATA table</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-335"; title="Batch
scanning over the !METADATA table can cause issues">ACCUMULO-335</a> Can't
batchscan over the !METADATA table</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-391";
title="Multi-table input format">ACCUMULO-391</a> Added support for reading
from multiple tables in a Map Reduce job.</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1018";
title="Client does not give informative message when user can not read
table">ACCUMULO-1018</a> Client does not give informative message when user can
not read table</li>
-<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1442";
title="Replace JLine with JLine2">ACCUMULO-1442</a> JLine2 support was added to
the shell. This adds features like history search and other nice things GNU
Readline has. </li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1492";
title="bin/accumulo should follow symbolic links">ACCUMULO-1492</a>
bin/accumulo should follow symbolic links</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1572";
title="Single node zookeeper failure kills connected accumulo
servers">ACCUMULO-1572</a> Single node zookeeper failure kills connected
Accumulo servers</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1661";
title="AccumuloInputFormat cannot fetch empty column family">ACCUMULO-1661</a>
AccumuloInputFormat cannot fetch empty column family</li>
@@ -163,7 +161,6 @@ TODO some bugs may be unintelligible to
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1698";
title="stop-here doesn't consider system hostname">ACCUMULO-1698</a> stop-here
doesn't consider system hostname</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1901";
title="start-here.sh starts only one GC process even if more are
defined">ACCUMULO-1901</a> start-here.sh starts only one GC process even if
more are defined</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1920";
title="monitor not seeing zookeeper updates">ACCUMULO-1920</a> Monitor was not
seeing zookeeper updates for tables</li>
-<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1921"; title="NPE
in tablet assignment">ACCUMULO-1921</a> NPE in tablet assignment</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1994"; title="Proxy
does not handle Key timestamps correctly">ACCUMULO-1994</a> Proxy does not
handle Key timestamps correctly</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2037";
title="Tablets not assigned to last location">ACCUMULO-2037</a> Tablets are now
assigned to the last location </li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2174"; title="VFS
Classloader has potential to collide localized resources">ACCUMULO-2174</a> VFS
Classloader has potential to collide localized resources</li>
@@ -194,7 +191,6 @@ mutation queues.</p>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2008"; title="Block
cache reserves section for in-memory blocks">ACCUMULO-2008</a> Block cache
reserves section for in-memory blocks</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2059";
title="Namespace constraints easily get clobbered by table
constraints">ACCUMULO-2059</a> Namespace constraints easily get clobbered by
table constraints</li>
</ul>
-<p>TODO look for other known issues</p>
<h2 id="documentation-updates">Documentation updates</h2>
<ul>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1218";
title="document the recovery from a failed zookeeper">ACCUMULO-1218</a>
document the recovery from a failed zookeeper</li>
