You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by bu...@apache.org on 2014/04/08 23:49:17 UTC
svn commit: r905501 - in /websites/staging/accumulo/trunk/content: ./
release_notes/1.6.0.html
Author: buildbot
Date: Tue Apr 8 21:49:17 2014
New Revision: 905501
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 Tue Apr 8 21:49:17 2014
@@ -1 +1 @@
-1585788
+1585843
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 Tue Apr 8 21:49:17 2014
@@ -94,6 +94,7 @@
<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>
<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>
@@ -130,6 +131,7 @@
<h3 id="service-ip-addresses">Service IP addresses</h3>
<p>Previous versions of Accumulo always used IP addresses internally. This could be problematic in virtual machine environments where IP addresses change. In <a href="https://issues.apache.org/jira/browse/ACCUMULO-1585" title="Use FQDN/verbatim data from config files">ACCUMULO-1585</a> this was changed, now the accumulo uses the exact hostnames from its config files for internal addressing. </p>
<p>All Accumulo processes running on a cluster are locatable via zookeeper. Therefore using well known ports is not really required. <a href="https://issues.apache.org/jira/browse/ACCUMULO-1664" title="Make all processes able to use random ports">ACCUMULO-1664</a> makes it possible to for all Accumulo processes to use random ports. This makes it easier to run multiple Accumulo instances on a single node. </p>
+<p>While Hadoop <a href="http://wiki.apache.org/hadoop/HadoopIPv6">does not support IPv6 networks</a>, attempting to run on a system that does not have IPv6 completely disabled can cause strange failures. <a href="https://issues.apache.org/jira/browse/ACCUMULO-2262" title="Include java.net.preferIPv4Stack=true in process startup">ACCUMULO-2262</a> invokes the JVM-provided configuration parameter at process startup to prefer IPv4 over IPv6.</p>
<h3 id="viewfs">ViewFS</h3>
<p>Multiple bug-fixes were made to support running Accumulo over multiple HDFS instances using ViewFS. <a href="https://issues.apache.org/jira/browse/ACCUMULO-2047" title="Failures using viewfs with multiple namenodes">ACCUMULO-2047</a> is the parent
ticket that contains numerous fixes to enable this support.</p>
@@ -139,7 +141,10 @@ ticket that contains numerous fixes to e
<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>
+<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1833" title="MultiTableBatchWriterImpl.getBatchWriter() is not performant for multiple threads">ACCUMULO-1833</a> Multitable batch writer is faster now when used by multiple threads</li>
+<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1933" title="Make unit on memory parameters case-insensitive">ACCUMULO-1933</a> Lower case can be given for memory units now.</li>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-2128" title="Provide resource cleanup via static utility rather than Instance.close">ACCUMULO-2128</a> Provide resource cleanup via static utility</li>
+<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
@@ -155,8 +160,8 @@ TODO some bugs may be unintelligible to
<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>
<li><a href="https://issues.apache.org/jira/browse/ACCUMULO-1696" title="Deep copy in the compaction scope iterators can throw off the stats">ACCUMULO-1696</a> Deep copy in the compaction scope iterators can throw off the stats</li>
<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-1833" title="MultiTableBatchWriterImpl.getBatchWriter() is not performant for multiple threads">ACCUMULO-1833</a> MultiTableBatchWriterImpl.getBatchWriter() is not performant for multiple threads</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-2174" title="VFS Classloader has potential to collide localized resources">ACCUMULO-2174</a> VFS Classloader has potential to collide localized resources</li>