Author: buildbot
Date: Mon Feb 16 21:17:51 2015
New Revision: 940397

Log:
Staging update by buildbot for accumulo

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

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb 16 21:17:51 2015
@@ -1 +1 @@
-1660194
+1660205

Modified: websites/staging/accumulo/trunk/content/release_notes/1.6.2.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.6.2.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.6.2.html Mon Feb 16 
21:17:51 2015
@@ -204,16 +204,31 @@ that client code that runs against 1.6.1
 the improvements with very little concern in change of underlying 
functionality. Users of 1.4 or 1.6
 are seeking to upgrade to 1.6 should consider 1.6.2 the starting point over 
1.6.0 or 1.6.1. For
 information about improvements since Accumulo 1.5, see the <a 
href="http://accumulo.apache.org/release_notes/1.6.0.html";>1.6.0</a> and <a 
href="http://accumulo.apache.org/release_notes/1.6.1.html";>1.6.1</a> release 
notes.</p>
+<h2 id="notable-bug-fixes">Notable Bug Fixes</h2>
+<h3 id="only-first-zookeeper-server-is-used">Only first ZooKeeper server is 
used</h3>
+<p>In constructing a <code>ZooKeeperInstance</code>, the user provides a 
comma-separated list of addresses for ZooKeeper
+servers. 1.6.0 and 1.6.1 incorrectly truncated the provided list of ZooKeeper 
servers used to the first. This
+would cause clients to fail when the first ZooKeeper server in the list became 
unavailable and not properly
+load balance requests to all available servers in the quorum. <a 
href="https://issues.apache.org/jira/browse/ACCUMULO-3218";>ACCUMULO-3218</a> 
fixes the parsing of
+the ZooKeeper quorum list to use all servers, not just the first.</p>
+<h3 id="incorrectly-handled-zookeeper-exception">Incorrectly handled ZooKeeper 
exception</h3>
+<p>Use of ZooKeeper's API requires very careful exception handling as some 
thrown exceptions from the ZooKeeper
+API are considered "normal" and must be retried by the client. In 1.6.1, 
Accumulo improved its handling of
+these "expected failures" to better insulate calls to ZooKeeper; however, the 
wrapper which sets data to a ZNode
+incorrectly handled all cases. <a 
href="https://issues.apache.org/jira/browse/ACCUMULO-3448";>ACCUMULO-3448</a> 
fixed the implementation of <code>ZooUtil.putData(...)</code> to handle
+the expected error conditions correctly.</p>
+<h3 id="scanid-is-not-set-in-activescan"><code>scanId</code> is not set in 
<code>ActiveScan</code></h3>
+<p>The <code>ActiveScan</code> class is the returned object by 
<code>InstanceOperations.listScans</code>. This class represents a
+"scan" running on Accumulo servers, either from a <code>Scanner</code> or 
<code>BatchScanner</code>. The <code>ActiveScan</code> class 
+is meant to represent all of the information that represents the scan and can 
be useful to administrators
+or DevOps-types to observe and act on scans which are running for excessive 
periods of time. <a 
href="https://issues.apache.org/jira/browse/ACCUMULO-2641";>ACCUMULO-2641</a>
+fixes <code>ActiveScan</code> to ensure that the internal identifier 
<code>scanId</code> is properly set.</p>
 <h2 id="performance-improvements">Performance Improvements</h2>
-<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>
+<p>Apache Accumulo 1.6.2 includes a number of performance-related fixes over 
previous versions.</p>
 <h3 id="improvement-1">Improvement 1</h3>
 <h3 id="improvement-2">Improvement 2</h3>
 <h2 id="other-improvements">Other improvements</h2>
 <h3 id="improvement-1_1">Improvement 1</h3>
-<h2 id="notable-bug-fixes">Notable Bug Fixes</h2>
-<h3 id="bug-fix-1">Bug fix 1</h3>
-<h3 id="bug-fix-2">Bug fix 2</h3>
 <h2 id="documentation">Documentation</h2>
 <p>The following documentation updates were made: </p>
 <h2 id="testing">Testing</h2>


Reply via email to