svn commit: r956000 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.5.3.html

[bu...@apache.org]

Author: buildbot
Date: Thu Jun 25 22:58:26 2015
New Revision: 956000

Log:
Staging update by buildbot for accumulo

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

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jun 25 22:58:26 2015
@@ -1 +1 @@
-1687660
+1687661

Modified: websites/staging/accumulo/trunk/content/release_notes/1.5.3.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.5.3.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.5.3.html Thu Jun 25 22:58:26 2015
@@ -220,10 +220,48 @@ in newer release lines.</p>
 this is a "patch version". This means that there have been no API changes. Any
 changes which were made were done in a backwards-compatible manner. Code that
 runs against 1.5.2 is guaranteed to run against 1.5.3.</p>
-<h1 id="major-changes">Major Changes</h1>
-<h1 id="performance-improvements">Performance Improvements</h1>
-<h1 id="other-improvements">Other improvements</h1>
+<p>We'd like to thank all of the committers and contributors which had a part in
+making this release from code contributions to testing. Everyone's efforts are
+greatly appreciated.</p>
+<h1 id="security-changes">Security Changes</h1>
+<h2 id="sslv3-disabled-poodle">SSLv3 disabled (POODLE)</h2>
+<p>Many Accumulo services were capable of enabling wire encryption using
+SSL connectors. 1.5.3 disables the problematic SSLv3 version which was
+susceptible to the man-in-the-middle attack.</p>
 <h1 id="notable-bug-fixes">Notable Bug Fixes</h1>
+<h2 id="sourceswitchingiterator-deadlock">SourceSwitchingIterator Deadlock</h2>
+<p>An instance of SourceSwitchingIterator, the Accumulo iterator which transparently manages
+whether data for a tablet read from memory (the in-memory map) or disk (HDFS after a minor
+compaction), was found deadlocked in a production system.</p>
+<p>This deadlock prevented the scan and the minor compaction from ever successfully completing
+without restarting the tablet server. ACCUMULO-3745 fixes the inconsistent synchronization
+inside of the SourceSwitchingIterator to prevent this deadlock from happening in the future.</p>
+<p>The only mitigation of this bug was to restart the tablet server that is deadlocked.</p>
+<h2 id="table-flush-blocked-indefinitely">Table flush blocked indefinitely</h2>
+<p>While running the Accumulo RandomWalk distributed test, it was observed that all activity in
+Accumulo had stopped and there was an offline Accumulo metadata table tablet. The system first
+tried to flush a user tablet, but the metadata table was not online (likely due to the agitation
+process which stops and starts Accumulo processes during the test). After this call, a call to
+load the metadata tablet was queued but could not complete until the previous flush call. Thus,
+a deadlock occurred.</p>
+<p>This deadlock happened because the synchronous flush call could not complete before the load
+tablet call completed, but the load tablet call couldn't run because of connection caching we
+perform in Accumulo's RPC layer to reduce the quantity of sockets we need to create to send data.
+ACCUMULO-3597 prevents this deadlock by forcing the use of a non-cached connection for the RPC
+message requesting a metadata tablet to be loaded.</p>
+<p>While this feature does result in additional network resources to be used, the concern is minimal
+because the number of metadata tablets is typically very small with respect to the total number of
+tablets in the system.</p>
+<p>The only mitigation of this bug was to restart the tablet server that is hung.</p>
+<h2 id="rpc-connections-not-cached">RPC Connections not cached</h2>
+<p>It was observed that the underlying connection for invoking RPCs were not actually being cached,
+despite it being requested that they should be cached. While this did not result in a noticed
+performance impact, it was deficiency. <a href="https://issues.apache.org/jira/browse/ACCUMULO-3574">ACCUMULO-3574</a> ensures that connections are cached when
+it is requested that they are.</p>
+<h2 id="deletes-on-thrift-proxy-api-ignored">Deletes on Thrift Proxy API ignored</h2>
+<p>A user noted that when trying to specify a delete using the Accumulo Thrift Proxy, the delete
+was treated as an update. <a href="https://issues.apache.org/jira/browse/ACCUMULO-3474">ACCUMULO-3474</a> fixes the Proxy server such that deletes are properly
+respected as specified by the client.</p>
 <h1 id="testing">Testing</h1>
 <p>Each unit and functional test only runs on a single node, while the RandomWalk
 and Continuous Ingest tests run on any number of nodes. <em>Agitation</em> refers to
@@ -247,12 +285,20 @@ Accumulo configuration from <code>120s</
     <th>Tests</th>
   </tr>
   <tr>
-    <td>N/A</tdt>
-    <td>N/A</td>
-    <td>N/A</td>
-    <td>N/A</td>
-    <td>N/A</td>
-    <td>N/A</td>
+    <td>Gentoo</tdt>
+    <td>2.6.0</td>
+    <td>1</td>
+    <td>3.4.5</td>
+    <td>No</td>
+    <td>Unit and Integration Tests</td>
+  </tr>
+  <tr>
+    <td>Centos 6.5</tdt>
+    <td>2.7.1</td>
+    <td>6</td>
+    <td>3.4.5</td>
+    <td>No</td>
+    <td>Continuous Ingest and Verify</td>
   </tr>
 </table>
   </div>