svn commit: r951794 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.7.0.html

[bu...@apache.org]

Author: buildbot
Date: Mon May 18 22:14:34 2015
New Revision: 951794

Log:
Staging update by buildbot for accumulo

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

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon May 18 22:14:34 2015
@@ -1 +1 @@
-1680113
+1680114

Modified: websites/staging/accumulo/trunk/content/release_notes/1.7.0.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.7.0.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.7.0.html Mon May 18 22:14:34 2015
@@ -302,19 +302,6 @@ Accumulo internals w/o impacting the API
 <p>Created an Accumulo API regular expression for use with checkstyle. Starting with 1.7.0, projects building on Accumulo can use 
 this checkstyle rule to ensure they are only using Accumulo's public API. The regular expression can be found in the 
 <a href="https://github.com/apache/accumulo/blob/8cba8128fbc3238bdd9398cf5c36b7cb6dc3b61d/README.md">README</a>.</p>
-<h3 id="balancing-groups-of-tablets">Balancing Groups of Tablets</h3>
-<p>By default Accumulo evenly spreads each tables tablets across a cluster.  In some 
-situations its advantageous for query or ingest to evenly spreads groups of tablets 
-within a table.  For <a href="https://issues.apache.org/jira/browse/ACCUMULO-3439">ACCUMULO-3439</a> a new balancer was added to evenly 
-spread groups of tablets.  This Apache <a href="https://blogs.apache.org/accumulo/entry/balancing_groups_of_tablets">blog post</a> provides more 
-details.</p>
-<h3 id="user-specified-durability">User-specified Durability</h3>
-<p>Prior to 1.7, a user could configure the durability for individual tables. With the implementation of
-<a href="https://issues.apache.org/jira/browse/ACCUMULO-1957">ACCUMULO-1957</a>, the durability can be specified by the user when creating a BatchWriter. 
-This can result in substantially faster ingest rates when the durability can 
-be relaxed, such as when power is redundantly available to the cluster.</p>
-<h3 id="wait-for-tablet-balance-api">Wait for tablet balance API</h3>
-<p>https://issues.apache.org/jira/browse/ACCUMULO-2998</p>
 <h2 id="notable-bug-fixes">Notable Bug Fixes</h2>
 <h3 id="sourceswitchingiterator-deadlock">SourceSwitchingIterator Deadlock</h3>
 <p>An instance of SourceSwitchingIterator, the Accumulo iterator which transparently
@@ -345,12 +332,45 @@ we can ensure that this deadlock won't o
 Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure
  dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat
  non proident, sunt in culpa qui officia deserunt mollit anim id est laborum</p>
-<h2 id="other-improvements">Other improvements</h2>
-<h3 id="improvement-1">Improvement 1</h3>
-<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
-Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure
- dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat
- non proident, sunt in culpa qui officia deserunt mollit anim id est laborum</p>
+<h2 id="general-improvements">General improvements</h2>
+<h3 id="balancing-groups-of-tablets">Balancing Groups of Tablets</h3>
+<p>By default Accumulo evenly spreads each tables tablets across a cluster.  In some 
+situations its advantageous for query or ingest to evenly spreads groups of tablets 
+within a table.  For <a href="https://issues.apache.org/jira/browse/ACCUMULO-3439">ACCUMULO-3439</a> a new balancer was added to evenly 
+spread groups of tablets.  This Apache <a href="https://blogs.apache.org/accumulo/entry/balancing_groups_of_tablets">blog post</a> provides more 
+details.</p>
+<h3 id="user-specified-durability">User-specified Durability</h3>
+<p>Prior to 1.7, a user could configure the durability for individual tables. With the implementation of
+<a href="https://issues.apache.org/jira/browse/ACCUMULO-1957">ACCUMULO-1957</a>, the durability can be specified by the user when creating a BatchWriter. 
+This can result in substantially faster ingest rates when the durability can 
+be relaxed, such as when power is redundantly available to the cluster.</p>
+<h3 id="waitforbalance-api">waitForBalance API</h3>
+<p>When creating a new Accumulo table, the common next step is to add splits to the
+table before starting ingest. This can be extremely important as a table without
+any splits will only be hosted on a single TabletServer. Adding many splits will
+ensure that a table is distributed across many servers.</p>
+<p>In previous versions, adding splits to a table is synchronous, but the assignment
+of those splits was asynchronous. <a href="https://issues.apache.org/jira/browse/ACCUMULO-2998">ACCUMULO-2998</a> adds a new method
+to <code>InstanceOperations</code> which allows users to wait for all tablets to be balanced.
+This method lets users wait until tablets are appropriately distributed so that
+ingest can be started unhampered.</p>
+<h3 id="hadoop-metrics2-support">Hadoop Metrics2 Support</h3>
+<p>Accumulo has long had its own metrics system integration using Java MBeans. This
+enabled metrics to be reported by Accumulo services, but consumption by other systems
+often required use of an additional tool like jmxtrans to read the metrics from the
+MBean and send them to some other system.</p>
+<p><a href="https://issues.apache.org/jira/browse/ACCUMULO-1817">ACCUMULO-1817</a> switches Accumulo to replace the custom MBean code
+with Hadoop Metrics2. Metrics2 has a number of benefits, the most common of which
+is invalidating the need for an additional process to send metrics to common metrics
+storage and visualization tools. With Metrics2 support, Accumulo can send its
+metrics to common tools like Ganglia and Graphite.</p>
+<h3 id="distributed-tracing-with-htrace">Distributed Tracing with HTrace</h3>
+<p>HTrace has recently started gaining traction as a standlone-project, especially
+with its adoption in HDFS. Accumulo has long had distributed tracing support
+via its own "Cloudtrace" library, but wasn't intended to use outside of Accumulo.</p>
+<p><a href="https://issues.apache.org/jira/browse/ACCUMULO-898">ACCUMULO-898</a> replaces Accumulo's Cloudtrace code with HTrace. This
+has the benefit of timings (spans) already in Accumulo automatically containing
+additional information from the HDFS operations.</p>
 <h2 id="documentation">Documentation</h2>
 <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
 Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure